Power saving mechanisms in nr

ABSTRACT

Methods, systems, and devices may assist in power saving in new radio. For example, enable power savings during the connected mode discontinuous reception cycle of the RRC_CONNECTED state of a user equipment.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication No. 62/737,266, filed on Sep. 27, 2018, entitled “PowerSaving Mechanisms In NR,” and U.S. Provisional Patent Application No.62/825,226, filed on Mar. 28, 2019, entitled “Power Saving Mechanisms InNR,” the contents of each are hereby incorporated by reference herein intheir entirety.

BACKGROUND

The connected mode discontinuous reception (CDRX) cycle in 3GPP LTERel,15 and 3GPP NR Rel.15: In 3GPP LTE, the UE wakes up prior to the ONduration of the CDRX cycle and resynchronizes to the signal to be readyto receive grants. The OnDuration is configured to the UE through RRC.The UE monitors every slot for PDCCH. If no grant is received or notransmission must be done during the slot, the UE may sleep during theremaining symbols of the slot. Similarly, in 3GPP NR Rel. 15, the UEmonitors for PDCCH on the configured monitoring occasion in the DRX ONstate. It can go to sleep during the other symbols. But in both systems,the UE must monitor the PDCCH on the next occasion within the ONDuration and during the duration of the DrxInactivityTimer; so, themicro-sleep is short.

Power Saving Mechanisms in 3GPP NR Rel.15: 3GPP NR Rel. 15 introducedsome tools to improve power utilization at the UE. For example,adaptation of UE operation between narrow and wide BWPs enables UE toreceive PDCCH in a narrow CORESET and conserve power but dynamicallyreceive PDSCH/PUSCH in a wider BWP and then return to the narrow BWPwhen it does not have a grant.

Another feature called cross-slot scheduling allows a UE to receive aPDCCH grant in a slot but have grant resources in another slot; thisallows more processing time for the UE and it can reduce its powerutilization compared to same-slot scheduling.

SUMMARY

In the following discussions, the signal used to send the UE tomicro-sleep maybe referred to as a go-to-sleep (GTS) signal. The signalused to wake-up a UE that is in sleep mode is referred to as a wake-upsignal. The wake-up and GTS signals are referred to a power savingssignal in the remainder of the discussions. Although specific examplesmay apply to the wake-up signal or GTS, the solutions applicable to onesignal may also apply to the other signal.

Disclosed herein are methods, systems, and devices that may assist inpower saving in NR. The system may enable power savings during the CDRXcycle of the RRC_CONNECTED state of the UE and power savings whenmonitoring paging occasions during RRC IDLE and INACTIVE states. Beloware examples:

UE may enter the micro-sleep state for extended duration in the CDRXcycle. In micro-sleep state, the UE may not monitor PDCCH duringOnDuration. In micro-sleep state, the UE may not monitor PDCCH when theDrxInactivityTimer has not expired.

Micro-sleep may imply a low-power state with minimal monitoring on anarrow BWP. UE may monitor PDCCH or a trigger on a narrow BWP. UE mayprocess the granted resources (receives PDSCH/transmits PUSCH) on a wideBWP. UE may return to narrow BWP by default after processing the grantedresources.

UE may set a microsleepTimer and decrements it as it micro-sleeps. Whenthe timer expires, the UE may return to a wide BWP.

UE may have semi-static configuration of micro-sleep duration duringwhich it need not monitor its PDCCH monitoring occasions. UE has avalid-monitoring-window when it monitors for PDCCH. UE has micro-sleepwindow when it micro-sleeps. UE has alternating valid-monitoring-windowand micro-sleep window. No explicit indication is required forsleep/wake-up.

UE may be RRC configured to micro-sleep in the duration between the DCIgiving the grant and its granted resources.

UE may be RRC configured to micro-sleep for a fixed duration followingthe granted resources (for PDSCH/PUSCH).

UE receives dynamic indication of micro-sleep duration through thepower-signal PDCCH, such as through the RNTI or PDCCH resource location.

UE is activated with the Micro-sleep BWP where it can micro-sleep untilthe bwpInactivitytimer expires.

UE may have multiple micro-sleep BWPs to support different sleepdurations.

UE may enter a micro-sleep BWP in one of the following ways: 1) Throughactivation DCI for micro-sleep BWP; 2) On expiration ofBWPInactivityTimer for a wider BWP; or 3) On completion of processinggranted resources (PUSCH/PDSCH).

UE may have reduced blind decoding if the Aggregation level or PDCCHlocation in the CORESET are fixed for certain duration of time.

Micro-sleep may be indicated as a slot-format through DCI. It may beindicated through group common PDCCH or a UE-Specific DCI.

Power saving signals such as go-to-sleep (GTS) or wake-up signals may beindicated through a GC-PDCCH or UE-specific PDCCH. A single DCI may beused to indicate the wake-up or the GTS state depending on the contentof its payload. Alternatively, DCIs with one format may be used forsignaling GTS and another format may be used for indicating the wake-upstate.

The wake-up signal may occur prior to OnDuration of a DRX cycle in apre-onDuration-Window (POW) whose monitoring period is configured to theUE.

The wake-up signal may occur during the OnDuration of a DRX cycle or inthe active time of the DRX cycle.

The UE may perform aperiodic reporting or synchronization between thePOW and the DRX OnDuration.

The power saving signal may provide activation or deactivation ofcertain CORESETs or search spaces or dynamic DRX parameters.

The DMRS in a grant may be used as GTS signal. Change in the DMRSconfiguration may indicate the last grant after which the UE maymicro-sleep during the DRXInactivtyTimer.

The power saving signal may indicate the BWP that UE must wake-up on andperform monitoring during the OnDuration.

Multiple power savings States (PSC) may be configured for the UE. Anactive PSC may be indicated to the UE through RRC or MAC CE or an L1signaling such as the wake-up signal. A PSC may define a set of BWPs,DRX parameters which can be per BWP, TDRA table which can be per BWP,etc.

If different minimum KO values are configured for BWP1 and BWP2 and UEmust switch from one BWP1 to BWP2, it uses K0 values according to theTDRA definitions for BWP1 for the first grant in BWP2.

A default PSCD may be defined for UE. The UE switches from a non-defaultPSC, PSC1 to PSCD on expiration of a timer.

A UE may monitor an SCell in the “dormant state” with minimal or noPDCCH monitoring for power savings. The UE may transition its monitoringof the SCell to the activate state or deactivated state using an RRC orMAC CE based command or L1 signaling which may be received on that SCellor another cell such as the PCell or PSCell or another SCell.

The UE may transition from the active state to the dormant state when atimer set in the active state expires.

The UE may transition from the dormant state to a deactivated state whena timer set in the dormant state expires.

The UE autonomously activate dormant state cells when it sends an SR.The number of activated cells and the identity of the activated cellsmay depend on the type of traffic UE must support and the UE's BSR.

The UE may report the autonomously activated cells to the gNB.Alternatively, the gNB may preconfigure S SCells to be activated for agiven BSR value.

The UE may bundle S cells together such that certain behavior on onecell triggers certain behavior on the other cell sin the bundle. Forexample, a power savings signal may put the PCell into micro-sleep. Thistrigger the SCells in the bundle (with PCell) to also go to micro-sleep.

A wake-up signal on one Cell may trigger dormancy-to-active transitionon a bundled cell.

A wake-up signal on one Cell may trigger deactivated-to-dormant statetransition on a bundled cell.

A GTS on one cell may trigger dormancy-to-deactivated state transitionon a bundled cell.

A GTS on one cell may trigger micro-sleep on a bundled cell.

A GTS on one cell may trigger active-to-dormancy state transition on abundled cell.

BWP switching on once cell may trigger a corresponding BWP switching ona bundled cell.

A PSC activation on one cell may trigger activation of a correspondingPSC on a bundled cell.

UE-specific paging DCI may be used to reduce the false paging alarmwhere the DCI payload carries some bits of the UE ID and the DCI isscrambled with the other bits of the UE ID.

A wake-up or signal GTS such as OOK may be used to indicate if a UE mustwake-up or go to sleep at the start of a paging occasion.

Multiple paging RNTIs may be introduced such that a UE ID maps to one ormore of the paging RNTIs. If a UE receives a paging DCI scrambled withone of the paging RNTIs, it monitors the paging PDSCH.

Disclosed herein are methods, systems, and devices that may assist inenabling SCell activation, deactivation from a dormant state.

Disclosed herein are methods, systems, and devices that may assist inenabling bundled operation across multiple cells.

Disclosed herein are methods, systems, and devices that may assist inenabling power savings in IDLE and INACTIVE state.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter. Furthermore,the claimed subject matter is not constrained to limitations that solveany or all disadvantages noted in any part of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

A more detailed understanding may be had from the following description,given by way of example in conjunction with the accompanying drawingswherein:

FIG. 1A illustrates exemplary micro-sleep pattern in UE-Legacy systems

FIG. 1B illustrates exemplary micro-sleep pattern in UE-Disclosedextended-sleep by skipping certain monitoring occasions;

FIG. 2A illustrates exemplary micro-sleep with minimal monitoring—onBWPD for BWP_(W) activation;

FIG. 2B illustrates exemplary micro-sleep with minimal monitoring—sleepand wake-up through aperiodic CSI-RS trigger;

FIG. 2C illustrates exemplary micro-sleep with minimalmonitoring—wake-up on expiration of microSleepTimer;

FIG. 3A illustrates exemplary monitoring periodicity of NR Rel.15 UE;

FIG. 3B illustrates exemplary disclosed monitoring with micro-sleepwindow and valid-monitoring-window;

FIG. 4A illustrates exemplary micro-sleep based on reception of agrant-No PDCCH monitoring between the DCI and the granted resource;

FIG. 4B illustrates exemplary micro-sleep based on reception of agrant-No PDCCH monitoring for 2 slots after the granted resource;

FIG. 4C illustrates exemplary micro-sleep based on reception of agrant-No PDCCH monitoring in C occasions after a DCI that provides agrant;

FIG. 4D illustrates exemplary micro-sleep based on reception of agrant-No PDCCH monitoring within the DRX cycle after the indication ofthe last PDSCH in DRX cycle;

FIG. 5 illustrates exemplary dynamic indication of micro-sleep duration;

FIG. 6A illustrates exemplary indication of micro-sleep duration—asoffset from PDCCH monitoring occasion;

FIG. 6B illustrates exemplary indication of micro-sleep duration—asoffset from start of granted resource;

FIG. 7A illustrates exemplary activation of Micro-sleep BWP, BWP_(MS,m)through DCI-UE switches to BWP_(D) when it exits BWP_(MS,m);

FIG. 7B illustrates exemplary activation of Micro-sleep BWP, BWP_(MS,m)through DCI-UE returns to BWP_(W) when it exits BWP_(MS,m);

FIG. 8 illustrates exemplary activation of Micro-sleep BWP, BWP_(MS,m)on expiration of BWPInactivityTimer for BWP_(W); UE returns to BWPD whenits exits BWP_(MS,m);

FIG. 9 illustrates exemplary activation of Micro-sleep BWP, BWP_(MS,m)on completion of processing of granted resource (PDSCH/PUSCH); UEreturns to BWP_(W) when its exits BWP_(MS,m);

FIG. 10 illustrates exemplary reducing the blind decoding hypotheses byhaving same PDCCH AL and PDCCH location L within time Δt;

FIG. 11 illustrates exemplary display that may be generated based on themethods, systems, and devices of power saving in NR;

FIG. 12A illustrates exemplary PDCCH on first monitoring occasion inOnDuration as a wake-up signal—UE Behavior when it receives PDCCH;

FIG. 12B illustrates exemplary PDCCH on first monitoring occasion inOnDuration as a wake-up signal—UE Behavior when it does not receive thePDCCH;

FIG. 13A illustrates exemplary monitoring the power savings signal inthe POW—Monitoring in default BWP and switching to active BWP;

FIG. 13B illustrates exemplary monitoring the power savings signal inthe POW—Monitoring in active BWP;

FIG. 14A illustrates UE performs aperiodic CSI reporting on receivingthe wake-up signal.

FIG. 14B illustrates an exemplary method associated with UE performingaperiodic CSI reporting;

FIG. 14C illustrates another exemplary method associated with UEperforming aperiodic CSI reporting;

FIG. 15A illustrates exemplary power savings signals triggers CSIreporting priori to ONDuration-CSI reporting after the POW;

FIG. 15B illustrates exemplary power savings signals triggers CSIreporting priori to ONDuration-CSI reporting within the POW;

FIG. 16 illustrates exemplary default PSC, PSCD and PSC1 are PSCsconfigured to the UE;

FIG. 17 illustrates exemplary cross-slot scheduling;

FIG. 18 illustrates exemplary same slot scheduling with PUSCH startinglocation beginning after PDCCH decoding is completed

FIG. 19A illustrates exemplary PSC indication-Switching from PSC_(D) toPSC₁;

FIG. 19B illustrates exemplary PSC indication-Switching to PSC_(D) onexpiration of pscValidTimer;

FIG. 20 illustrates exemplary BWP based PSC switching;

FIG. 21A illustrates exemplary-switch to default BWP in active state;

FIG. 21B illustrates exemplary SCell activation from the formantstate-(B) switch to an active BWP in active state;

FIG. 22 illustrates exemplary UE procedure to switch a cell from activeto dormant using active TodormancyTimer;

FIG. 23 illustrates exemplary procedure for UE to switch from dormant todeactivated state;

FIG. 24 illustrates exemplary UE has 2 bundles of cells configured—onebundle with PCell and with PSCell;

FIG. 25 illustrates exemplary correspondence if PSCs between PCell and abundles SCell

FIG. 26 illustrates exemplary one cell may be included in multiplebundles;

FIG. 27 illustrates exemplary BWP-switch in PCell triggers a BWP-switchin SCell

FIG. 28 illustrates exemplary procedure for UE to activate a bundle ofcells;

FIG. 29 illustrates exemplary UE-specific paging DCI without PDSCH. DCIis scrambled with part of UE's ID and remaining part of UE ID is in thepayload of the DCI;

FIG. 30 illustrates exemplary UE-Specific paging DCI also providing aPDSCH grant to the UE;

FIG. 31 illustrates exemplary UE monitors R₁-RNTI, P₂-RNTI and P₄-RNTIout of the pool of paging RNTIs;

FIG. 32A illustrates exemplary communications system;

FIG. 32B illustrates exemplary system that includes RANs and corenetworks;

FIG. 32C illustrates exemplary system that includes RANs and corenetworks;

FIG. 32C illustrates exemplary system that includes RANs and corenetworks;

FIG. 32E illustrates another example communications system;

FIG. 32F is a block diagram of an example apparatus or device, such as aWTRU;

FIG. 32G is a block diagram of an exemplary computing system;

FIG. 33 illustrates exemplary display that may be generated based on themethods, systems, and devices herein;

FIG. 34A illustrates exemplary method for sleeping or waking up aftermonitoring the pre-onduration-window, such as UE wake-up detectingwake-up signal or otherwise sleeping;

FIG. 34B illustrates exemplary method for sleeping or waking up aftermonitoring the pre-onduration-window, such as UE sleeps on detecting theGTS signal; or otherwise it wakes-up for the onduration;

FIG. 34C illustrates exemplary method for sleeping or waking up aftermonitoring the pre-onduration-window, such as UE wakes-up if neither GTSnot wake-up signal is detected or uses default power savingsconfiguration;

FIG. 35 illustrates exemplary DRX InactivityTimer running during thepre-onduration-window duration;

FIG. 36A illustrates exemplary method for active period runs intomonitoring the pre-onduration-window, such as UE monitors the nextOnDuration even if DRXInactivityTimer expires prior to OnDuration;

FIG. 36B illustrates exemplary method for active period runs intomonitoring the pre-onduration-window, such as UE sleeps at the start ifthe next OnDuration if DRXInactivityTimer expired prior to OnDuration;

FIG. 37 illustrates exemplary method for when an active period runs intomonitoring the pre-onDuration-window, such as UE receives power savingsignal in the active duration;

FIG. 38A illustrates exemplary method for receiving GTS in the activeduration, such as UE sleeps for some duration and wakes up to continuemonitoring during the active session;

FIG. 38B illustrates exemplary method for receiving GTS in the activeduration, such as UE's active duration terminates and UE sleeps and UEwakes up to monitor next POW on next OnDuration;

FIG. 39 illustrates exemplary fields and locations of the fields withinthe DCI;

DETAILED DESCRIPTION

Micro sleep extension in RRC_CONNECTED state issue. It is establishedthat successive UL grants, successive DL grants and successive UL-DL orsuccessive DL-UL grants typically occur sparsely. The average durationbetween 2 UL grants is 10 ms, between 2 DL grants is 14 ms, and betweena UL-DL grant is 6 ms. NR should consider ways to extend the micro-sleepduration during CDRX of the RRC-CONNECTED state of the UE by exploitingthe duration between consecutive scheduling. It is well understood thatPDCCH monitoring is a significant contributor to baseband powerconsumption. Frequency of monitoring, number of hypotheses to blinddecode and bandwidth of the CORESET are all contributing factors. NRshould consider ways to rapidly adapt PDCCH monitoring to trafficconditions to enable efficient micro-sleep.

Power savings on the SCell issue. In conventional situations, UE's powerconsumption on SCell may be significant during the state when an SCellis activated. As the activation and deactivation of an SCell occursthrough the MAC CE, it is not dynamic and is a relatively slow process,taking several 10s of milliseconds. It is desired to make the activationand deactivation more dynamic so that the UE may quickly adapt its powerconsumption to the traffic load. So, any approach is disclosed herein toaddress power consumption during monitoring on the SCell.

Power consumption during paging issue. Conventionally, in the IDLE andINACTIVE states, the UE may perform cell measurements and monitor forthe paging DCI. When monitoring for the paging DCI, the UE may monitormultiple beams (if it can receive multiple beams). If there is no pagingDCI, it may go to sleep. If there is a paging DCI, it decodes the PDSCHto see if it has been paged. If it has not been paged, e.g. it is afalse paging alarm, it may go to sleep. In a heavily loaded cell, falsepaging alarm rate can be high and can contribute to significant powerconsumption for the UE. Monitoring for the paging DCI in the pagingoccasions is also a factor in UE power consumption in the IDLE state.

Micro-sleep extension in RRC_CONNECTED state is disclosed herein. ThegNB may introduce the “micro-sleep” state during the CDRX cycle in theRRC_CONNECTED state; micros-sleep can occur during the OnDuration orwhen the DrxInactivityTimer has not expired. The UE may micro-sleepduring the time that it does not receive grants. For example, the UE maymicro-sleep in the last few slots of a DrxInactivityTimer duration orduring the PDCCH monitoring occasions between two successive grants. Themicro-sleep enables the UE to turn off various components of its modem(RF, baseband and various power islands) and achieve power savings.

Unlike legacy systems like LTE and NR Rel.15, this disclosure enablesthe UE to skip monitoring certain configured monitoring occasions duringthe CDRX. FIG. 1A shows an example of micro-sleep in LTE and NR Rel.15;the UE has a CDRX OnDuration during which it receives a grant and setsit DrxInactivtyTimer and begins to decrement it. If theDrxInactivtyTimer has not expired, the UE monitors every monitoringoccasion configured to it. It resets the timer on receiving a grant. Ifthe UE does not have a grant or does not have to transmit PUCCH/SRS, orprocess CSI-RS, it may micro-sleep during those symbols of the slot. Thepower profile of the UE is shown in the figure; the UE monitors PDCCH onevery slot in the OnDuration and duration of the DrxInactivtyTimer. Evenif there is no traffic on several slots during the OnDuration or theduration of the DrxInactivtyTimer, the UE must be awake to monitorPDCCH.

FIG. 1B shows an example of the UE's timeline and power consumption forthe micro-sleep disclosed herein; the UE has an extended micro-sleepacross multiple slots during the duration of the DrxInactivtyTimer,e.g., it skips some monitoring occasions. By not waking up on everymonitoring occasion within the CRDX duration, the UE saves more power.The extent of power savings in micro-sleep can vary depending on theduration of micro-sleep, frequency of ramp-up, functions to performduring the ramp-up (such as resynchronization), etc.

Micro-sleep with minimal monitoring: The micro-sleep state could bedefined to support minimal monitoring, e.g., UE monitors some signals ina low power state. The UE may be equipped with a specialized low powerstate hardware for a lower power state signal monitoring. The lowerpower state signal (or equivalently micro-sleep indication) may be abinary state signal which indicates to the UE whether or not to be inmicro sleep state; The frequency resource for this signal may be a“skinny” BWP which may be significantly narrower than the initial BWP orthe default BWP.

Alternatively, minimal monitoring may occur in the form of PDCCHmonitoring on a narrow BWP. Besides, the PDCCH monitoring period may belong to keep the power consumption low. The UE may be configured to usea specific aggregation level (AL) for the PDCCH or a specific PDCCHlocation to significantly reduce the number of blind-decodinghypotheses—this can be supported in low traffic modes, if large numberof resources are available.

The UE may receive a DCI with a grant on the narrow BWP and it switchesto a wide BWP to receive/transmit on the granted resources, e.g., theDCI activates a wide BWP. After processing the granted resources(PUSCH/PDSCH), the UE may return to the narrow BWP to continuemonitoring PDCCH.

The concept is shown in FIG. 2A. Here the micro-sleep occurs on thenarrow BWP which may be the default BWP and referred to as BWPD. The UEmay monitor the PDCCH at the rate of once every 2 slots. When itreceives a grant from the DCI, it switches to a wide BWP referred to asBWP_(W). It receives PDSCH or transmits PUSCH on BWP_(W). On completion,the UE returns to micro-sleep on BWPD. So, the UE may not wait for adeactivation DCI or for the bwpInactivitytimer to expire on the BWP_(W)when it switches back to BWPD.

Alternatively, the UE may monitor a DL preamble or aperiodic CSI-RS oraperiodic TRS triggered through a DCI. On receiving this signal ortrigger, UE may enter micro-sleep or wake-up. If aperiodic CSI-RS basedtrigger is used, the following procedures may apply: First, the sequenceof the aperiodic CSI-RS indicates that the UE should sleep and theduration of the sleep. Secondly, the sequence of the CSI-RS indicatesthat the UE should wake-up in a particular BWP. Thirdly, on receivingthe DCI trigger for aperiodic CSI-RS, the UE may sleep; it need notreceive the aperiodic CSI-RS signal. In fact, the gNB may only transmitthe triggering DCI but not the aperiodic CSI-RS. Furthermore, the UE maynot need to transmit an aperiodic CSI-RS report for that trigger. Andfourthly, the trigger for waking up the UE may be in the form of anaperiodic Tracking Reference Signal (TRS). On waking up, the UE canreacquire fine timing and frequency using the aperiodic TRS.

The gNB may configure the sequences used for indicating micro-sleep andsleep duration, the sequences for wake-up, or the correspondingtransmission resources through RRC to the UE. But the indication ofmicro-sleep or wake-up may come dynamically through the aperiodic CSI-RStrigger, or other physical layer control signal(s). The concept is shownin FIG. 2B. The UE may receive the aperiodic CSI-RS trigger on BWP_(W)indicating it to micro-sleep for some duration. So, the UE may switch toBWPD and micro-sleep with minimal monitoring; it periodically monitorsPDCCH for the wake-up trigger providing an aperiodic TRS. When the UEreceives the trigger, it may switch back to BWP_(W) and use theaperiodic TRS to fine tune its timing and frequency. In this scenario,the UE may rely on an explicit wake-up signal to wake-up.

As an alternative, the UE may run a timer microSleepTimer for a certainduration. It sets the timer to a value configured through RRC, and afunction of the triggered aperiodic CSI-RS. It may decrement the timeruntil it expires. On expiry, the UE may wake up. The UE may monitorBWP_(W) or BWPD on wake-up. This concept is shown in FIG. 2C. Here theaperiodic CSI-RS sequence is tied to certain microSleepTimer durationwhich is configured to the UE through RRC. Depending on the indicatedCSI-RS, the UE sets the microSleepTimer. It may wake up to monitorBWP_(W).

Alternatively, the UE uses the specialized low power state hardware tomonitor the micro-sleep signal in every PDCCH monitoring occasionsduring the time that include the time while the on-duration timer isrunning, or the inactivity timer is running or other active timeperiods. The UE may perform micro-sleep between PDCCH monitoringoccasions if the micro-sleep signal bit is set to micro-sleep.

Adapting Micro-sleep by altering the monitoring period: One way totailor micro-sleep to the traffic pattern is by adapting the PDCCHmonitoring occasions, e.g., UE need not monitor certain occasions wherea grant will not be received. The search space monitoring periodicitymay be updated according to the traffic; it can be configured to besparser but this reduces the scheduling flexibility of the gNB. Instead,the gNB has more flexibility if UE supports normal monitoringperiodicity when a grant is likely to occur, so that there is finergranularity of opportunities for the gNB to transmit the DCI.

Semi-static configuration of micro-sleep: The gNB may semi-staticallyconfigure micro-sleep parameters for the UE. Micro-sleep for M ms,referred to as a sleep-window, is supported. The UE may go tomicro-sleep in the sleep-window. This is followed by PDCCH monitoringwithin a monitoring window of W ms, referred to as thevalid-monitoring-window, e.g., the UE can expect to receive PDCCHproviding a grant within the valid-monitoring-window. The sleep-windowand valid-monitoring-window alternate for the UE. This operation may beapplied especially in light traffic conditions, when resources are notin shortage, and the gNB has flexibility to manage the occurrence of thenext PDCCH for the UE. This concept is shown in FIG. 3A and FIG. 3B. AUE not configured for micro-sleep has the PDCCH monitoring occasions asshown in FIG. 3A, e.g., the UE monitors every configured PDCCHmonitoring occasion at the periodicity of 1 slot. Whereas, a UEconfigured with sleep-window and valid-monitoring-window has monitoringoccasions as shown in FIG. 3B. The micro-sleep window is a mask appliedto the monitoring occasions in the search space; it masks certainoccasions from being monitored so that the UE can micro-sleep and savepower.

Grant-based Micro-sleep behavior: Furthermore, a UE behavior may bedefined to support micro-sleep between the PDCCH giving a grant and thetime of occurrence of the granted resources. This can be applied toscenarios of cross-slot grants where K0>0. The concept is shown in FIG.4A where, the UE receives a grant with K0=2. The UE does not monitor thePDCCH occasions between the DCI and the granted resources.

FIG. 4B shows another UE behavior wherein, the UE may micro-sleep overduration M ms immediately following the granted resources. Here M=2 ms;the UE does not monitor the PDCCH occasions in the 2 slots following thegranted resources. After M ms, the UE wake up without the need foradditional wake-up indication and continues to monitor PDCCH. Thesebehaviors may be RRC configured to the UE using a flag (or otherindicator) that indicates if the UE must follow such a micro-sleepprocedure.

As another alternative to the case described in FIG. 4A, the UE may skipmonitoring C PDCCH monitoring occasions after detecting a DCI carrying avalid non-zero grant for it or may skip monitoring the PDCCH occasionsin S slots after detecting a DCI carrying a valid non-zero grant for it.The value of C or S may be RRC configured to the UE. The concept isshown in FIG. 4C, where the UE receives a cross-slot grant with K0=3 andC=2; so UE is not required to monitor PDCCH in 2 slots following theDCI. This allows the UE to wake up from a micro-sleep just in time toreceive the PDCCH and PDSCH occurring together in slot #3.

The DMRS in a PDSCH may be used to indicate a potential lasttransmission in a CDRX cycle, so that the UE may sleep if itsuccessfully decodes it; in this case, the UE may micro-sleep throughthe remainder of the DRX cycle even if the DRXInactivityTimer has notexpired. The UE may wake up to start monitoring on the next DRX cycle.The DMRS may indicate the last transmission in the following ways. In afirst way, a UE may be configured with maximum number of front-loadedDM-RS symbols for PDSCH as maxLength=2. The scheduling DCI indicates thenumber of front-loaded DMRS symbols dynamically through a DCI field.Disclosed herein is a UE procedure such that when the DCI indicates thevalue of number of front-loaded DMRS symbols as ‘numFLDMRS’, the UE mayassume it is the last transmission in that C-DRX cycle. The parameternumFLDMRS may be configured to the UE through RRC signaling. Forexample, this mode of operation may be used only if an RRC parameterpowerSavingsThroughDMRS is configured through RRC signaling to the UE.In another way, if the number of front-loaded DMRS symbols changesbetween two successive grants, the UE may read as an indication to sleepuntil the start of the next DRX cycle as shown in FIG. 4D.

Dynamic micro-sleep indication: The gNB may dynamically indicate themicro-sleep duration to the UE. The dynamic indication can come throughfollowing signal examples. In a first example, RNTI of the PDCCH may bemasked with a sequence that indicates the micro-sleep window duration.The UE may decode the DCI with the candidate masks. If the DCI decodessuccessfully, the candidate mask is used to determine the micro-sleepduration. The masks and corresponding micro-sleep durations may beconfigured with the UE through RRC. The configuration could becell-specific as all UEs may be configured at the same time with thesame set of masks. In a second example, the starting location of theresource of the PDCCH may indicate the micro-sleep window parameter. ThegNB may have more flexibility to support this in light trafficconditions.

The procedure for dynamic indication is described below and illustratedin FIG. 5. The UE receives an indication dynamically to micro-sleep fora certain duration. The UE then wakes-up and continues to monitor thePDCCH. If the UE misses to decode a PDCCH, it may not go to micro-sleep.Other than the micro-sleep duration, the parameters associated with theindication could be following offsets as shown in FIG. 6A or FIG. 6B.First, offset from the start of the micro-sleep duration from the PDCCHmonitoring occasion as shown in FIG. 6A. The offset may be in terms ofslots or mini-slots. Second, offset from the start of the grantedresources as shown in FIG. 6B. The offset may be in terms of slots ormini-slots.

The dynamic indication to wake-up or micro-sleep may also provideactivation or deactivation of a CORESET or a search space for someduration. If a CORESET is activated, the UE may need to wake-up tomonitor it. If a CORESET is deactivated, the UE may micro-sleep; thenthe UE need not monitor that CORESET and may micro-sleep when possibleduring the duration of the CORESET. A field may be present in the powersaving signal (if it is a DCI) indicating the impacted CORESET and theits activation, deactivation status. If the UE has a single CORESETconfigured in the C-DRX ONDuration, then one bit is sufficient to denoteits activation and deactivation.

If a UE supports both eMBB and URLLC traffic, it may be configured witha search-space of high periodicity to allow frequent monitoring of URLLCgrants. If the gNB determines that the UE does not have URLLC traffic inthe short term, it may signal the UE to deactivate that search space.Activation and deactivation of CORESETs and search spaces may comethrough the wake-up signal or GTS on L1. An UL or DL grant may also beused to indicate activation or deactivation of a CORESET or searchspace.

A field may be introduced in the DCI providing the grant to indicate theactivation and deactivation for a CORESET or search space.

CORESET activation/deactivation and search space activation/deactivationmay also be enabled through MAC CE.

Micro-sleep activation through a “Micro-sleep BWP”: A UE may micro-sleepin a BWP without resources—such a BWP is referred to as micro-sleep BWP.Activation of micro-sleep BWP can be done through a DCI with format suchas 0_0 or 0_1 or 1_0 or 1_1 and scrambled with the UE's C-RNTI and byindicating the BWP ID (bwp-ID). Existing procedures for BWP can be usedto put the UE in the micro-sleep state during the duration whenmicro-sleep BWP is active. On switching to the micro-sleep BWP, the UEmay set the timer BWPInactivityTimer with an RRC configured value anddecrements the timer. As no resources are allowed for this BWP, theremay be no CORESET to monitor; so, the UE may have extended micro-sleepfor the duration of this timer. Note that the micro-sleep BWP may not bedeactivated through DCI as there may be no resources in this BWP.

Multiple micro-sleep BWPs: A UE may be configured through RRC with Mmicro-sleep BWPs, each with a different value for theBWPInactivityTimer; this may give flexibility to the gNB to schedule adifferent duration of micro-sleep to the UE depending on the trafficconditions, UE's power sensitivity, user load, etc. Currently in NR, asingle value of bwp-InactivityTimer is RRC configured for all BWPs of aUE. However, different values of bwp-InactivityTimer are supported forthe M micro-sleep BWPs. So, the BWP information element may be given bythe following, such as in Table 1.

TABLE 1 BWP information element -- ASN1START -- TAG-BANDWIDTH-PART-STARTBWP ::= SEQUENCE {  locationAndBandwidth   NULL,  subcarrierSpacing NULL,  cyclicPrefix  NULL  OPTIONAL -- Need R } BWP-Downlink ::= SEQUENCE {  bp-Id  BWP-Id,  bwp-InactivityTimer   ENUMERATED {ms2, ms3,ms4, ms5, ms6, ms8, ms10, ms20,     ms30,ms40,ms50, ms60, ms80, ms100,ms200,     ms300, ms500, ms750, ms1280, ms1920, ms2560,     spare10,spare9, spare8, spare7, spare6,     spare5, spare4, spare3, spare2,spare1 }     OPTIONAL,  bp-Common   BWP-DownlinkCommon      OPTIONAL,   -- Need M  bwp-Dedicated    BWP-DownlinkDedicated    OPTIONAL, --Need M  ...   }   BWP-Uplink ::=  SEQUENCE {  bwp-Id  BWP-Id, bwp-InactivityTimer   ENUMERATED {ms2, ms3, ms4, ms5, ms6, ms8, ms10,ms20,     ms30,ms40,ms50, ms60, ms80, ms100, ms200,     ms300, ms500,ms750, ms1280, ms1920, ms2560,     spare10, spare9, spare8, spare7,spare6,     spare5, spare4, spare3, spare2, spare1 }     OPTIONAL, bwp-Common     BWP-UplinkCommon     OPTIONAL,   -- Need M  bp-Dedicated   BWP-UplinkDedicated    OPTIONAL,  -- Need M  ... } --TAG-BANDWIDTH-PART-STOP -- ASN1STOP

The bwp-InactivityTimer parameter is configured in the BWP-Uplink orBWP-Downlink for BWP-Ids that correspond to micro-sleep BWPs. This valuemay override that from the ServingCellConfig Information Element for themicro-sleep BWPs.

UE procedure for operating in a micro-sleep BWP: The switch tomicro-sleep may be triggered by one of the following mechanisms, each ofwhich is further described in more detail herein: 1) Micro-sleep inBWP_(MS,m) though activation DCI; 2) Micro-sleep in BWP_(MS,m) onBWPInactivityTimer expiration on BWP_(W); or 3) Micro-sleep inBWP_(MS,m) following the processing of granted resources.

The terminology BWPg may be used to refer to a general BWP of the UE.BWPg may be a default BWP BWPD or a wide BWP BWPW.

Micro-sleep in BWP_(MS,m) though activation DCI: The UE may receive anactivation DCI on BWP_(g) for the m^(th) micro-sleep BWP, BWP_(MS,m).The UE may enter the micro-sleep state and set the BWPInactivityTimeraccording to the configuration for BWP_(MS,m) and then may decrement it.As the UE cannot receive PDCCH in BWP_(MS,m) to activate/deactivate aBWP, the UE may stay in this state until the BWPInactivityTimer expires.Then the UE may perform one of the following procedures. In a firstexample procedure with reference to FIG. 7A, when BWPInactivityTimerexpires in BWP_(MS,m), the UE may switch to BWPD and may monitor PDCCHon the default BWP, which may be like minimal monitoring in micro-sleep.The UE may ignore the resource allocation fields in the activation DCIwhen it identifies the bwp-ID as that of a micro-sleep BWP. The conceptis shown in FIG. 7A where the UE monitors PDCCH on BWP_(W) and mayreceive activation DCI for BWP_(MS,m) with K0=0. So, the UE may startmicro-sleep in the same slot, e.g., switches to BWP_(MS,m) and staysthere until its BWPInactivityTimer expires. On expiration, the UE mayswitch to BWPD. In a second example procedure with reference to FIG. 7B,when BWPInactivityTimer expires in BWP_(MS,m), the UE may return toBWP_(g). The concept is shown in FIG. 7B where the UE monitors PDCCH onBWP_(W) and receives activation DCI for BWP_(MS,m) with K0=0. So, the UEmay switch in the same slot to BWP_(MS,m) and may stay there until itsBWPInactivityTimer expires. On expiration, the UE may return to BWP_(W).If the UE failed to decode the activation DCI, the result may not becatastrophic; the UE may spend more energy by not going to themicro-sleep state but stays on BWP_(g). On returning to BWP_(g) afterBWPInactivityTimer expires in BWP_(MS,m), the UE may handle theBWPInactivityTimer on BWP_(g) in the following exemplary ways. In afirst way, the BWPInactivityTimer is set for BWP_(g) and started. In asecond way, the UE may save the BWPInactivityTimer's value t_(g) at thetime of switching to BWP_(MS,m). The UE may set the BWPInactivityTimerto t_(g) on switching back to BWP_(g) after the micro-sleep. In a thirdway, the UE may save the BWPInactivityTimer's value t_(g) at the time ofswitching to BWP_(MS,m). The UE may set the BWPInactivityTimer tot_(g)-t_(elapsed) on switching back to BWP_(g) after the micro-sleep.t_(elapsed) is the total time that elapsed between switching toBWP_(MS,m) and switching back to BWP_(g).

Micro-sleep in BWP_(MS,m) on BWPInactivityTimer expiration on BWP_(W):The UE's BWPInactivityTimer on BWP_(W) may trigger the UE to switch toBWP_(MS,m). The gNB may configure the BWP_(MS,m) to be used for a givenBWP_(W). The concept is shown in FIG. 8, where BWP_(W) is activated tothe UE through a DCI on BWPD. The UE's BWPInactivityTimer set forBWP_(W) expires, upon which the UE transitions to BWP_(MS,m). Here itsets the BWPInactivityTimer according to the configuration forBWP_(MS,m) and starts it. When the timer expires, the UE may switch toBWPD. In this case, the scheduling may typically occur in BWPD but thegranted resource may be received and processed in the wider BWP_(W).

Micro-sleep in BWP_(MS,m) following the processing of granted resources:When the UE completes the processing of a PDSCH or a PUSCH transmission,the UE may automatically switch to a BWP_(MS,m). The gNB may configurethe BWP_(MS,m) to be used for a given BWP_(W). The concept is shown inFIG. 9, where the UE completes processing the granted resources onBWP_(W). Then the UE may automatically switch to BWP_(MS,m). When theBWPInactivityTimer expires on BWP_(MS,m), the UE switches back toBWP_(W). On returning to BWP_(W), the UE may handle theBWPInactivityTimer in the following ways. In a first way, theBWPInactivityTimer may be set as per the configuration for BWP_(W) andstarted. In a second way, the UE may save the BWPInactivityTimer's valuet_(g) at the time of switching to BWP_(MS,m). The UE may set theBWPInactivityTimer to t_(g) on switching back to BWP_(W) after themicro-sleep. In a third way, the UE may save the BWPInactivityTimer'svalue t_(g) at the time of switching to BWP_(MS,m). The UE may set theBWPInactivityTimer to t_(g)-t_(elapsed) on switching back to BWP_(W)after the micro-sleep. t_(elapsed) is the total time that elapsedbetween switching to BWP_(MS,m) and switching back to BWP_(W).

UE behavior during BWP_(MS,m): In NR, when a specific BWP is activated,the UE must switch to it. However, disclosed herein are procedures thatmay be more flexible for micro-sleep BWPs. The UE may consider anindication to switch only as a recommendation to switch to themicro-sleep BWP. The UE may do one of the following procedures when itis recommended to switch to a BWP_(MS,m). A first procedure may include,the UE switching to BWP_(MS,m) and staying in micro-sleep until itstimer expires. A second procedure may include a UE remaining on thecurrent BWP (it may be the active BWP, for example, BWP_(W) or BWPD) forsome or all of the duration of the timer of BWP_(MS,m). Then it maycontinue to perform the procedure that it would have done if it hadswitched to and exited BWP_(MS,m). For example, UE may do CSI-RSmeasurements on BWP_(W) even though it received the indication to switchto BWP_(MS,m). A third procedure may include, a UE may switch to anotherBWP for doing measurements for some or all of the duration of the timerof BWP_(MS,m). Then it may continue to perform the procedure that itwould have done if it had switched to and exited BWP_(MS,m).

It is expected that the UE is not required to do CSI-RS measurement orcertain PUCCH transmissions such as periodic CSI-RS reporting. UE mayalso not be expected to do SR transmission during the micro-sleep inBWP_(MS,m). However, if UE has SR resources configured on certain BWPsuch as BWPD during the duration of BWP_(MS,m), the UE may stay awakeand transmit SR on it.

Power savings through reduced blind decoding: Currently, NR Rel. 15defines certain aggregation levels (AL) for a search space; the UEblindly decodes the candidates with the configured ALs to detect theDCI. Supported herein is a UE behavior where the UE may assume that theAL of the PDCCH of time ‘T’ that was successfully decoded is applicablefor PDCCH occurring up to time T+Δt. So, the UE need not try other ALhypotheses for PDCCH monitoring occasions within time Δt. Δt isconfigured to the UE through RRC. This may be supported when sufficientresources are available and traffic is low in the system.

Similarly, if the UE detected a PDCCH candidate of certain AL at time Twith starting frequency resource location L (in the 1st symbol of theCORESET), it may assume the same location L and AL for the duration. At,so that it only needs to decode one candidate in the duration. At eachmonitoring occasion. This is shown in FIG. 10, where the AL and Ldetected in PDCCH at time T applies to all PDCCH within T+Δt.

Indication of micro-sleep as a slot format: Supported herein is anindication of micro-sleep in the form of a slot format. The indicationto micro-sleep can come through the format 2_0 DCI scrambled withSFI-RNTI. The slot format is defined by an index into a table of formatsfor DL, UL and flexible symbols denoted by ‘D’, ‘U’ and ‘X’ respectivelyin 3GPP NR Rel. 15 specification. The SFI-RNTI provides the slot formatfor N slots by indicating the index for each of the N slots.

Introduced herein is a new type of symbol ‘M’ in the slot-format whichindicates that the UE can micro-sleep in that symbol. The DCI of format2_0 with SFI-RNTI can indicate the index of the new slot format withentries of ‘M’. On receiving the DCI, the UEs configured with SFI-RNTImay enter micro-sleep on the symbols indicated by the DCI. As SFI-RNTIis a group common PDCCH, this disclosure allows for micro-sleepindication in a multicast manner.

Some examples of slot formats with symbols marked with the state ‘M’ aregiven in Table 2. The whole slot can be indicated for micro-sleep or amini-slot may be indicated for micro-sleep.

The index is currently 8 bits in 3GPP Rel.15 for slot format indication,but not all values of the index are defined. So, introducing new slotformats with state ‘M’ can reuse the undefined entries for the slotformat and no extra bits are required.

This type of indication helps to manage micro-sleep at finerresolutions. Especially if a UE is configured with multiple monitoringoccasions in a slot, the UE's micro-sleep cannot be long and deep as ithas to wake up multiple times in the duration of the slot to monitor thePDCCH. This approach provides the ability to set the micro-sleep at afiner granularity of symbol level, so that micro-sleep can be managed atmini-slot resolutions.

TABLE 2 Slot formats with micro-sleep state ‘M’ for normal cyclicprefix. Symbol number in a slot Format 0 1 2 3 4 5 6 7 8 9 10 11 12 13100 M M M M M M M M M M M M M M 101 D M M M M M M M M M M M M M 102 D DM M M M M M M M M M M M 103 D D D M M M M M M M M M M M 104 D D D D D DD M M M M M M M 105 M M M M M M M M M M M M U U 106 M M M M M M M U U UU U U U

Alternatively, a new UE specific DCI scrambled with the C-RNTI may beintroduced to indicate the slot-format with micro-sleep indication. Forexample, the UE may receive the SFI for micro-sleep on format 2_0 DCIusing C-RNTI instead of the SFI-RNTI. This DCI may be received in thecommon search space similar to that of the SFI-RNTI. Alternatively, thisDCI may be scrambled with another RNTI called microsleep-RNTI “MS-RNTI”that is configured to the UE through RRC. MS-RNTI may be configured tobe common to multiple UEs.

The gNB may transmit a subsequent SFI-RNTI with states that may conflictwith those received by the UE through C-RNTI or MS-RNTI basedmicro-sleep indication. Alternatively, gNB may provide UE-specificgrants that conflict with micro-sleep pattern from a prior indication.In this case the following predefined rules may be used to determine if‘M’ can be overwritten by other states in SFI-RNTI or by the grants. Ina first rule, UE used the override from SFI-RNTI if the override occursis at least ‘R’ symbols away from the time the SFI-RNTI is received.This ensures that the UE has enough time to react to the override. In asecond rule, if D overrides M, explicitly (through SFI-RNTI) orimplicitly (through a DL grant), the UE follows the most recent controlsignaling and treats it as Tr. In a third rule, if ‘U’ overrides ‘M’,explicitly (through SFI-RNTI) or implicitly (through an UL grant), theUE follows the most recent control signaling and treats it as ‘U’.

Often the UE needs to micro-sleep for multiple symbols at a time.Disclosed herein is an indication through the SFI DCI that may bereinterpreted by the UE to imply that one symbol in the table indicatesmultiple adjacent symbols (mini-slot) or slots to the UE. This allowsthe DCI to indicate the micro-sleep status for multiple mini-slots orslots using a single index. Some examples are shown in Table 3. Herehalf a slot is denoted by a single state. When the state is X, itimplies that the SFI indication must be used for that half slot. Whenthe state is M, the UE may micro-sleep in that half slot.

TABLE 3 Slot formats with states representing half a slot Symbols in aslot 0- 7- 0- 7- 0- 7- 0- 7- 0- 7- 0- 7- 0- 7- 6 13 6 13 6 13 6 13 6 136 13 6 13 Slot Slot Slot Slot Slot Slot Slot Slot Slot Slot Slot SlotSlot Slot Format 1 1 2 2 3 3 4 4 5 5 6 6 7 7 100 X X X X X M M M M M M MM M

To minimize the blind decoding, further disclosed herein is this DCIindicating the micro-sleep in the slot format that may be transmittedonly in the first K monitoring occasions within the OnDuration. K=1 maybe a typical use case, where the UE monitors for this DCI only in thefirst occasion within the OnDuration.

Subsequently, the DCI may be transmitted when the DrxInactivtyTimer hasnot expired, outside the OnDuration. The DCI may be transmittedperiodically with period P that may be less than that of the monitoringperiodicity of its search space. The value of P is configured to the UEthrough RRC.

The DCI may provide the micro-sleep pattern for the duration of theentire C-DRX cycle.

If a UE has a grant or has to do measurement or transmit SR or SRS orPRACH, the UE may stay wake to process that function even if the SFIindicates ‘M’ on those symbols.

UE Assisted Micro-Sleep: The UE may provide assistance information tothe NB, so that the NB can properly configure the UE for micro-sleep.For e.g., the UE may signal the NB, its micro-sleep support capabilityinformation. Such information may indicate to the NB whether or not theUE supports micro-sleep feature. Furthermore, such information mayinclude support for one or more of the methods described herein. The UEmay also signal to the NB, its preferences for micro-sleep. For example,a UE with battery level below a minimum threshold, may indicate to theNB, that it would like to be put into micro-sleep mode. Similarly, a UEwith battery level above a certain maximum threshold or connected to apower source may indicate to the NB, that it would like to be taken outfrom micro-sleep mode or it doesn't want to be put into micro-sleepmode.

The UE may offer to the user a Graphical User Interface (GUI) thatallows the users to set preferences that controls micro-sleep. For e.g.,a lower power mode setting or battery saving setting by the user on theUE GUI may result in exchanges between the UE and the NB, and the NBordering the UE to perform micro-sleep.

On-off keying (OOK) based power savings signal: A simple OOK signal maybe used as a wake-up signal preamble. A simple receiver may be requiredto do envelope detection of OOK, potentially in the time domain andpower consumption is likely to be minimal for monitoring such a signal.An analog only receiver may be used to monitor an OOK signal and wake-upsection of the digital modem when it positively detects the OOK signal,e.g., the detected power exceeds certain threshold or a correlationexceeds certain threshold. Alternatively, the OOK signal may bemultiplexed with the channels in the time-frequency resource grid ofOFDM symbols. The OOK signal for wake-up or sleep indication in the RRCCONNECTED state may be preconfigured to the UE through RRC signaling.

The OOK signals may be UE-specific or common to multiple UEs. A UEwake-up when it receives a wake-up-OOK configured to it. A UEmicro-sleeps when it receives a GTS-OOK configured to it. UE-specificOOK signals may provide more optimal power savings by reducing falsewake-up alarms but if the number of resources are limited, multiple UEsmay share the same OOK.

A UE may also be configured with multiple wake-up-OOKs. If it receivesany one of the OOK signals it may wake-up. Alternatively, if it receivesall the wake-up OOKs within a predefined period of time, only then itwakes-up. Alternatively, if it receives at least W of Z configured.

OOKs, then it wakes up. These methods provide different levels ofrobustness against false wake-up alarms, thereby optimizing powersavings to different extents.

In configuring an OOK signal, the gNB may provide the sequence,frequency resources, and monitoring window to the UE.

For NR-U, in order to satisfy the OCB requirement, The OOK may be mappedto enough REs that satisfy the frequency occupation requirement.

DRX and wake-up signal-Receiving wake-up signal during the OnDuration ofa DRX cycle: The UE may wake up when its OnDuration occurs and monitorsthe wake-up signal. Here specifically considered is that the wake-upsignal may be in the form of a PDCCH, although other signals such asDMRS, CSI-RS, SSS, PSS, or a preamble may be used as a power savingssignal. The first PDCCH monitoring occasion may be used to indicate thatthe UE must stay awake to monitor PDCCH in the remaining OnDuration. Ifthe UE detects a wake-up signal PDCCH, it recognizes that it must wakeup, otherwise, the UE may go to sleep and does not monitor otheroccasions in the OnDuration. So, a PDCCH in the first monitoringoccasion of the OnDuration may act like a wake-up signal for the UE.

The concept is shown in FIG. 12. In FIG. 12A, the first PDCCH monitoringoccasion in the OnDuration gives the UE a PDSCH grant; so, the UEimplicitly recognized that it must wake up and continues to monitorthrough the OnDuration and through the occasions when theDrxInactivityTimer is running. In FIG. 12B, the UE does not detect aPDCCH in the first PDCCH monitoring occasion. So it goes to sleep untilthe next OnDuration.

This concept may be generalized so that the wake up signal may occur inthe form of a PDCCH within N monitoring occasions within the OnDurationof a DRX cycle.

The PDCCH may provide a grant to the UE, thus the UE identifies that itmust continue monitoring. Alternatively, the PDCCH may not be in theform of a grant but may be another DCI such as the one scrambled withMS-RNTI and providing the micro-sleep state to the UE.

Described herein is a way to minimize the blind decoding during thePDCCH decoding in the first occasion of the OnDuration; the location Lor aggregation level (AL) may be configured to the UE in advance throughRRC for the first monitoring occasion in the OnDuration. So, the UE mayhave minimal blind decoding overhead.

DRX and wake-up signal-Receiving wake-up signal before the OnDuration:It may be beneficial to allow the wake-up signal to be received prior tothe OnDuration so that the UE may do fine synchronization and beamtraining if required prior to the OnDuration. So the wake-up signal maybe transmitted in a pre-OnDuration-Window (POW) prior to an OnDuration.The concept is shown in FIG. 13.

If the wake-up signal is in the form of a PDCCH or DMRS followed byPDCCH, the UE may have a ‘WakeUp-CORESET’ configured for the wake-upsignal. This CORESET may have wideband DMRS to enable better detectionreliability for the DCI. But the CORESET may be relatively narrowbandwithin the default or active BWP to minimize the power consumption inmonitoring the Wake-up signal. A new DCI format may be introduced, suchas for wake-up signaling, and the UE may be configured to receive thewake-up signal in a user-specific search space or a common search space.As is contemplated with other optional considerations herein, it iscontemplated that both the user-specific search space and the commonsearch space may be configured to received the wake-up signal.

The UE may have multiple monitoring occasions within a POW, e.g., thesearch space periodicity for a DCI based wake-up signal may be smallenough that multiple occasions may occur in the POW. This providesflexibility to the gNB to address a large number of UEs. Outside theWakeUp-CORESET, the UE need not monitor the power savings signal.

FIG. 13A shows an example where the UE monitors POW on the default BWPBWPD and switches to an active BWP BWP_(A) on receiving a wake-upsignal, including a command to switch to BWP_(A) in POW. FIG. 13B showsan example where the UE monitors the POW in the active BWP BWP_(A) andsubsequently wakes up to monitor PDCCH on the DRX cycle of the same BWP.

The UE may micro-sleep between the duration that it receives the wake-upsignal and the start of the OnDuration. This may apply to the case wherethe UE does not see the need for resynchronization prior to OnDuration,for example if a BWP switch is not required on waking up or ifsynchronization accuracy is sufficient to operate in the BWP to whichthe UE is switched on reception of the wake-up signal.

Note that the periodicity of POW may be such that UE may monitor it onceevery D DRX cycles.

If the wake-up signal is received within this window, the UE mustwake-up at least to monitor the following OnDuration. If the wake-upsignal is not received within this window, the UE does not need to wakeup until the next POW occasion—this may be an implicit indication tosleep. This procedure is shown in FIG. 34A. At step 211, UE (e.g., WTRU102 a or UE 99) may monitor the POW. At step 212, there is adetermination made of whether a wake-up signal is detected. For example,this determination may be made based on whether a DL control signalcarrying the wake-up command is detected. If there is a determinationthat the wake-up signal has not been detected, then the UE may sleepuntil next POW (step 215). At or about the next POW, the monitoring ofstep 212 may continue to occur. At step 213, based on a determinationthat a wake-up signal is detected, then indicated parameters (e.g.,parameters from wake-up signal) may be used in the wake-up state. Atstep 214, UE may wake-up for the following OnDuration.

Alternatively, a GTS signal may be transmitted in the POW; on receivingit, the UE sleeps for the following OnDuration. If the GTS is notdetected, the UE must wake-up for the OnDuration of the following DRXcycle. This procedure is shown in FIG. 34B. At step 221, UE (e.g., WTRU102 a) may monitor the POW. At step 222, there is a determination madeof whether a GTS signal is detected. For example, this determination maybe made based on whether a DL control signal carrying the GTS command isdetected. If there is a determination that the GTS signal has beendetected, then the UE may sleep until next POW (step 224). At or aboutthe next POW, the monitoring of step 221 may occur. At step 223, basedon a determination that a GTS signal is detected, then UE may wake-upfor the following OnDuration.

In another example, a wake-up signal or GTS must be received by the UEto determine its behavior during the OnDuration of the following DRXcycle, as shown in the procedure in FIG. 34C. At step 231, UE (e.g.,WTRU 102 a) may monitor the POW. At step 232, there is a determinationmade of whether a GTS signal is detected. For example, thisdetermination may be made based on whether a DL control signal carryingeither the wake-up command or a GTS command is detected. If there is adetermination that the GTS signal has been detected, then the UE maysleep until next POW (step 236). At or about the next POW, themonitoring of step 231 may occur. At step 233, there is a determinationmade of whether a wake-up signal is detected. For example, thisdetermination may be made based on whether a DL control signal carryingthe wake-up command is detected. If there is a determination that thewake-up signal has not been detected, then based on this determination,at step 237, default parameters may be used in wake-up state. At step234, based on a determination that the wake-up signal has been detected,then indicated parameters (e.g., parameters from wake-up signal) may beused in the wake-up state. At step 235, then UE may wake-up for thefollowing OnDuration.

With continued reference for FIG. 34C and additional perspective, if aGTS signal is received, and the GTS indicates the duration of sleep, theUE sleeps for one or more DRX cycles. Instead, if the UE receives awake-up signal, it may wakeup for the following OnDuration. If thewake-up signal provides certain power savings parameters such as searchspace monitoring period etc., the UE may use those parameters fordetermining its operation following the wake-up. If it does not detectwake-up signal or GTS, it still may wake-up for the following OnDurationbut operates using a set of default values which would otherwise beprovided through the wake-up signal (if received). The default valuesmay be configured to the UE through RRC signaling.

Without in any way unduly limiting the scope, interpretation, orapplication of the claims appearing herein, a technical effect of one ormore of the examples disclosed herein is to provide adjustments to howpower is managed. While the conventional DRX mechanism allows UE tosleep and save power when it is not required to monitor the cell, DRXparameters cannot be adjusted dynamically according to the network'straffic or application. The methods described herein allow dynamicadaptation of the wake-up and sleep states for the UE—these states canbe adapted to suit the network's traffic and UE's applications

In FIG. 35, another scenario is shown where the active DRX time mayextend into the duration of a following POW. Then the followingoperational procedures may be considered for the UE. If the UE is inDRXInactivityTimer period during a POW occasion, the UE may assume thatthe gNB will not transmit a wake-up signal on the POW. So the UE neednot monitor the Wake-up CORESET during its DRXInactivityTimer period,e.g., UE may not monitor the wake-up signal during its active DRX time.So, the UE may not explicitly receive a wake-up signal in the POW forthe following OnDuration. In this case, one of the following proceduresmay occur. In a first example procedure, by default, the UE may monitorthe following OnDuration without receiving an explicit wakeup-signal.This procedure is shown in FIG. 36A. The UE may receive a GTS from thegNB indicating it to sleep and end that active DRX time. In a secondexample, the UE may sleep after the DRXInactivityTimer expires. It doesnot wake-up to monitor the following OnDuration as it did not monitorthe preceding POW. It may monitor the next available POW for an explicitwake-up signal. This procedure is shown in FIG. 36B. Further descriptionof the steps of FIG. 36A and FIG. 36B are shown below.

FIG. 36A illustrates an exemplary method for active period runs intomonitoring the pre-onduration-window, such as UE monitors the nextOnDuration even if DRXInactivityTimer expires prior to OnDuration. Atstep 241, there is a determination whether POW has reached a threshold.Based on the POW duration threshold being met, at step 242, there is adetermination of whether DRXInactivityTimer is running. Based on theDRXInactivityTimer running, at step 243, then UE may determine not tomonitor POW for power saving signal and then, at step 244, wake-up fornext DRX OnDuration, even if DRXInactivityTimer has expired. It shouldbe also noted that, if at step 242, there is a determination thatDRXInactivityTimer is not running, then at step 245, the UE may monitorPOW for power savings signal.

FIG. 36B illustrates an exemplary method for active period runs intomonitoring the pre-onduration-window, such as UE sleeps at the start ifthe next OnDuration if DRXInactivityTimer expired prior to OnDuration.At step 251, there is a determination whether POW has reached athreshold. Based on the POW duration threshold being met, at step 252,there is a determination of whether DRXInactivityTimer is running. Basedon the DRXInactivityTimer running, at step 253, then UE may determinenot to monitor POW for power saving signal and then, at step 254, sleepfor next DRX OnDuration, if DRXInactivityTimer expires. It should bealso noted that, if at step 252, there is a determination thatDRXInactivityTimer is not running, then at step 255, the UE may monitorPOW for power savings signal.

FIG. 37 illustrates an exemplary method for when an active period runsinto monitoring the pre-onDuration-window, such as UE receives powersaving signal in the active duration. If a UE is in the active DRX time,it may monitor the wake-up signal on a CORESET that it is configured formonitoring during its active time. If the wake-up signal is received,the UE may ensure that it is awake to monitor the following OnDurationas shown in the procedure in FIG. 37. At step 261, there is adetermination whether POW has reached a threshold. Based on the POWduration threshold being met, at step 262, there is a determination ofwhether DRXInactivityTimer is running. Based on the DRXInactivityTimerrunning, at step 263, then the UE may monitor for power saving signalduring the active time. It should be also noted that, if at step 262,there is a determination that DRXInactivityTimer is not running, then atstep 264, the UE may monitor POW for power savings signal.

With continued reference to FIG. 37, in an example, if the UE is in theactive DRX time, it may monitor the wake-up signal on a CORESET that itis configured for monitoring during its active time. If the wake-upsignal is received, the UE may ensure that it is awake to monitor thefollowing OnDuration as shown in the procedure in FIG. 37. The UE maymonitor the wake-up signal in its active time only during certainmonitoring occasions since it is not expected to receive a wake-upsignal soon after the UE sets its DRXInactivityTimer. A suitable time tosignal the wake-up signal may be close to the end of theDRXInactivityTimer expiration. Accordingly, the UE may monitor thewake-up signal only on K monitoring periods prior to theDRXInactivityTimer expiration. In an example alternative, a GTS may besignalled in the active time to indicate the UE to sleep during that DRXcycle, but the GTS may indicate the UE to wake-up for the nextONDuration. In another example alternative, the UE may monitor the powersavings signal during the duration of the POW but on CORESETscorresponding to the active duration (e.g., these CORESETs could bedifferent from the WakeUp-CORESET). During the active time, the powersavings signal may be signaled in UE-specific search space while in theinactive time, it may be signalled in a common search space, such asthat for a group-common PDCCH. The UE may reset its DRXInactivityTimeron receiving the wakeup-signal.

FIG. 38A illustrates an exemplary method for receiving GTS in the activeduration. There may be a scenario in which the active DRX active timeextends into a following OnDuration period. In this case, the activetime overlaps with the OnDuration and the UE is already awake during theOnDuration of that DRX cycle. The UE relies on the DRXInactivityTimerexpiration or the GTS signal to go to sleep during that cycle.

With reference to FIG. 38, at step 271, the GTS may be received by theUE any time during its active time. At step 272, the UE may determinethat the GTS may indicate the UE to micro-sleep for some duration and,at step 273, wake up within the active time to continue monitoringPDCCH. In this case, the DRXInactivityTimer may be decremented duringthe micro-sleep—this behavior of the timer keeps the current operationalprocedures of the UE unchanged. Alternatively, the DRXInactivityTimermay be suspended or frozen for the duration of the micro-sleep—thisprocedure may be useful to target use cases where the grants are sparseand UE can save power between the grants without early expiration of theDRXInactivityTimer. The duration of sleep may be indicated through theGTS signal or may be configured to the UE in advance through RRCsignaling.

FIG. 38B illustrates an exemplary method for receiving GTS in the activeduration, such as UE's active duration terminates and UE sleeps and UEwakes up to monitor next POW on next OnDuration. Alternatively, at step281 of FIG. 28B, the GTS may be received by the UE during its activetime, but based on the GTS being received, at step 282, then the UE mayend active time of that DRX cycle and go to sleep. The GTS may indicatethe UE to sleep until the next OnDuration occasion or the next POWoccasion. So, the UE's DRXInactivityTimer may expire and the UE goes tosleep as its active time in that DRX cycle ends.

At step 283, behavior of the UE in response of receipt of GTS in activetime (whether it wakes up in the same active time or wakes up only atthe start of the next POW or OnDuration) may be configured through RRCsignaling or indicated by the GTS signal.

The duration of the POW and periodicity for monitoring the POW may beconfigured to the UE through RRC signaling from the gNB. The startingtime of the POW may be indicated as an offset (e.g., in terms ofsymbols, mini-slots, or slot or a combination thereof) with respect tothe start of the OnDuration of the DRX cycle. Alternatively, thestarting time of the POW may be indicated as an offset with respect tothe frame timing. The monitoring occasions of the power saving signalwithin the POW is configured through the search space associated withthe CORESET (such as the WakeUp-CORESET). The configurations for POW maybe per BWP per cell and provided through RRC signaling from the gNB.

In general, a power savings signal received on BWP₁ may indicate thethat the UE must wake up in BWP₂. Or it may indicate that the UE mustmicro-sleep on BWP₂, e.g., UE micro-sleeps and subsequently may wake upon BWP₂ if it does not return to the BWPD.

On receiving a wake-up signal, prior to the start of the OnDuration inBWP₂, the UE may prepare to receive and transmit in BWP₂ and thereforemay perform one or more of the following on BWP₂ in the time gap betweenreception of the wake-up signal and OnDuration on BWP₂: 1) finesynchronization using TRS or PT-RS or other RS such as CSI-RS, DMRS,SSB; 2) beam training; or aperiodic CSI measurement and reporting—Thewakeup signal may provide an UL grant triggering aperiodic CSImeasurement such may be a DCI such as a format 0_1.

Alternatively, the UE may be configured to treat the wake-up signalitself as a trigger to do aperiodic CSI measurement or reporting inBWP₂. So the wake-up signal may implicitly trigger measurement orreporting. CSI-RS resources for measurement and PUCCH or PUSCH resourcesfor reporting are preconfigured to the UE; for example, thisconfiguration may indicate resources PUSCH starting slot or symbol withrespect to the slot or symbol start of the POW or the slot or symbol ofthe wake-up signal or the slot or symbol of the DRX OnDuration. Thewake-up signal itself may come in the form a group-common signal or aUE-specific signal in this example.

The concept of triggering aperiodic reporting is shown in FIG. 14A. Theprocedure is summarized in the following steps as shown in FIG. 14B. Atstep 301, UE may monitor POW occasions for power savings signal in BWPD.At step 302, if the signal is received by the UE, it may trigger aswitch to BWP_(A). At step 303, UE measures CSI-RS for aperiodicreporting. At step 304, UE reports CSI-RS during the OnDuration. At step305, UE receives a grant from the gNB during that C-DRX cycle.

Another example, as shown in FIG. 14C, is described in the followingprocedure may also be considered to trigger aperiodic reporting. At step311, UE monitors POW occasions for power savings signal in BWPD. At step312, if the signal is received by the UE, it may trigger a switch toBWP_(A). At step 313, UE measures CSI-RS for aperiodic reporting. Atstep 314, UE reports CSI-RS prior to the OnDuration. At step 315, UEreceives a grant from the gNB during the OnDuration of the C-DRX cycle.

The concept is shown in FIG. 15A. The CSI-RS can occur within the POW oroutside the POW.

CSI-RS reporting may also occur within the POW. This concept is shown inFIG. 15B. Here the measured CSI-RS in also with the POW.

Switching between power saving states: A UE may be configured withmultiple ‘power savings configurations’ (PSC). Depending on the UE'scapability or traffic conditions or application or feedback from the UE,a specific PSC may be applied, thereby providing a certain amount ofpower savings. Layer-1 or MAC CE or RRC may indicate the PSC to be usedin the UE.

A PSC may consist of one of more of the following parameters: 1)multiple BWPs, different DRX parameters, or time domain resourceallocation (TDRA) parameters. The concept is shown in FIG. 16. FIG. 16illustrates default PSC, PSC_(D) and PSC1 are PSCs configured to the UE.RRC signaling or MAC CE based configuration or L1 signaling may be usedto select a PSC.

Multiple BWPs—In a PSC multiple BWPs may be configured with differentparameters. Different extent of power savings can be obtained based onthe number of PRBs in a BWP. Also K0, K1, K2 values may be configuredsuitably to enable cross-slot scheduling and delayed scheduling within aslot to reduce buffering requirements immediately following the PDCCHmonitoring. The default BWP may be different for each PSC.BWPInactivityTimer may be configured differently for each BWP. Also, theCORESETs configured for each BWP may support different bandwidths andsearch space periodicities.

Different DRX parameters—A PSC may have a different duration for the DRXparameters such as DRXInactivtyTimer or OnDuration depending on theapplication. Furthermore, the DRX parameter may be BWP specific.

Time Domain Resource Allocation (TDRA) parameters—the PDSCH duration,starting time, etc. may influence the UE's buffering capabilities andthereby impact power consumption.

When a specific PSC is indicated, the UE uses certain BWPs, associatedDRX parameters, TDRA configuration. A default PSC ‘PSC_(D)’ may beconfigured to the UE.

If an application changes or traffic conditions change, it would bedesirable to switch the UE to operate in a suitable PSC configuration.For example, one PSC configuration may allow higher capacity and lowerlatency but less power savings. Whereas another PSC may trade capacityand latency for more power savings.

In order to micro-sleep, the UE can take advantage of a priori knowledgeof parameters such as KO. If K>0, the UE may micro-sleep between thePDCCH reception or processing and the PDSCH reception or processing asshown in FIG. 17. By not having to buffer the PDSCH while processing thePDCCH, the UE may save power.

In the state of the art, multiple KO values are configured through RRCsignaling. The DCI proving the PDSCH grant indicates the specific KOvalue for that grant. The UE may assume the worst case value for KO,e.g., the smallest KO value in the TDRA table to plan PDSCH bufferingand processing while optimizing its micro-sleep duration. Note thatpower savings may be enabled by a priori knowledge of KO; if KO is knownonly at the end of DCI decoding, the UE may not have enough time toreact to PDSCH buffering in a power efficient manner. In other words, UEshould prepare for the smallest value of KO.

Similarly, same slot scheduling can also reduce the constraints onbuffering if there sufficient time between PDCCH reception and thescheduled PDSCH reception (K0=0) and provide power savings. This type ofscheduling is shown in FIG. 18. But UE needs to know the CORESETduration and location within the slot and the starting point of thePDSCH that may be scheduled by a PDCCH in that CORESET. TheStart-and-Length-Indicator value (SLIV) for the grant may be configuredbased on the location of the CORESET in the slot and number of symbolswithin the CORESET.

Consider the use case where a UE supports both URLLC and eMBB traffic.eMBB traffic using relaxed values for KO can provide power savings whileURLLC traffic using smaller KO values for latency may have limited powersavings. So, the minimum KO value for eMBB may be greater than theminimum KO value for URLLC traffic. As another example, depending on itsload, the gNB may support different levels of power savings for a givenUE; it may operate with relaxed values of KO when the load is low andobtain significant power savings while it may use smaller values of KOwhen the load is high with less power savings. So, the minimum KO valuefor the low load case may be greater than the minimum KO value for highload case.

To support different PSCs, multiple TDRA tables may be configured to theUE supporting different set of KO values and different SLIVs.

The below example scenarios that may enable L1 based switching betweenthe PSCs. In the absence of any indication, the UE may use the defaultPSC PSC_(D). In a first scenario, the wake-up signal may indicate thePSC to be applied in that DRX ON cycle. For example, the wake-up signalmay indicate that only eMBB traffic is expected; in this case UE usesPSC₁. Or it may indicate that both eMBB and URLLC traffic are expectedso UE that uses PSC₂. The wake-up signal may be a GC-PDCCH orUE-specific PDCCH with a field indicating the PSC for the following DDRX cycles. If the wake-up signal is received in a POW, the UE may havesufficient time to switch the PSC. FIG. 19A shows an example where theUE switches from PSC_(D) to PSC₁ on receiving the wake-up signal. If thewake-up signal is received in OnDuration of a DRX cycle, the UE may alsobe simultaneously monitoring the CORESET for a grant and may use thedefault PSC for the BWP at least for the duration over which it mayreceive an indication for the PSC. Alternatively, it may use PSC_(p)configured by a wake-up signal in a past DRX cycle. Alternatively, apscValidTimer timer may be configured to the UE with its valueconfigured by RRC. The UE sets the timer upon receiving a PSC indicationfor PSC_(p). When the timer expires, the UE switches to the PSC_(D) asshown in FIG. 19B.

In a second scenario that may enable L1 based switching between thePSCs, multiple BWPs are configured for the UE, and each BWP may have itsown TDRA table. A PSC is associated with a BWP. The UE may activate BWPswitching to change the PSC. For example, BWP₁ may be configured withrelaxed KO values for supporting power savings with eMBB traffic. BWP₂may be configured with a small minimum KO value for supporting URLLC andeMBB. When URLLC traffic is granted, the gNB switches the UE from BWP₁to BWP₂. BWP₁ and BWP₂ may be identical except for the TDRA table. Sothe UE need not perform resynchronization or tuning and can startoperating on the new BWP without a lag. An UL or DL grant on BWP₁provides the indication to switch. But the UE may use the definition ofTDRA, KO and SLIV values based on BWP₁ for this grant. Subsequent grantsin BWP₂ may use the TDRA, KO and SLIV values configured for BWP₂. Thisconcept is shown in FIG. 20. FIG. 20 illustrates exemplary BWP based PSCswitching. K0=1 is used for the grant received from BWP₁ for PDSCH inBWP₂.

A third scenario that may enable L1 based switching between the PSCs, aPSC switching DCI may be used to change the PSC configuration on a BWP.It may be signaled as a GC-PDCCH or UE-specific PDCCH. It carries afield indicting the new PSC to be used, and a field indicating the timefrom when the switch must be applied.

In general, multiple PSCs can be activated at a given timer for a UE ifthe parameters impacted by the PSC do not overlap with other. Forexample, one PSC may impact the DRX and BWP. Another PSC may impact theTDRA table. Both these PSCs may be activated to the UE. This gives thegNB more flexibility to support different traffic types and providefiner resolutions of power savings with minimal configuration overhead.

SCell procedures for power savings—Low power operation in SCell: A newstate called the ‘dormant state’ may be introduced to enable the UE tosave power compared to the nominal operation where a UE switches betweenactive and deactivate states. A UE often stays in the active state asthe latency to deactivate and reactivate is high. The dormant state isstate of operation with operational load between that in the active anddeactivated states and therefore has less power consumption than in theactive state. Fast transitions between the states may enable powersavings by responding quickly to dynamic changes in the traffic.

The UE may have one or more SCells in the dormant state when it is inthe RRC-Connected mode. The UE may perform one or more of the followingoperations in the dormant cell. With regard to a first operation,measurements and tracking, reporting may occur through the PCell orPSCell.

With regard to a second operation in the dormant cell, minimal or noPDCCH monitoring on the SCell. In the dormant state, no grants arereceived on the SCell. The UE may not even monitor PDCCH on the SCell.When the SCell must be activated, the activation may be indicated on thePCell or PSCell through higher layer signaling or through L1 signaling.Alternatively, the UE may monitor PDCCH or activation-RS on the SCell inthe dormant state; when it receives an activation DCI or theactivation-RS, it activates the SCell and switches to active statemonitoring.

Disclosed herein is a dormant-BWP, dormant-CORESET, ordormant-search-space that may be configured for the UE to monitor PDCCHin the dormant state. Power savings may be achieved in thedormant-CORESET monitoring stage by restricting the number of blinddecodes, restricting the lengths and formats of DCIs to be expected. Forexample, UE may monitor only one DCI format for SCell activation ordeactivation in the dormant state. The DCI may be an UL grant triggeringan aperiodic CSI measurement report. Or it may be a DL grant or a PDCCHorder to enable timing advance for the UE. Alternatively, it may be aGC-PDCCH providing the activation or deactivation command to a group ofUEs.

The UE performs the following procedures when switching the cell fromthe dormant state to the active state. This procedure in shown in FIG.21A-FIG. 21B. UE 99 monitors the dormant-BWP for indication of cellactivation. UE 99 may also monitor PCell or PSCell for the cellactivation indication from gNB 98, for example. When the UE receives thecell-activation indication (at step 321 or step 331), it switches to theactive state, which may imply the following.

With reference to FIG. 21A, UE 99 may start monitoring the default BWPof the SCell (step 322). Note that the default BWP in the active cellstate and the dormant-BWP in the dormant cell state can denote the sameBWP.

With reference to FIG. 21B, the cell-activation DCI may indicate the BWPto be monitored in the cell. So, UE starts monitoring that active BWP(step 331 message sent including active BWP) once it switches to theactive cell state as shown in FIG. 21B. When it switches to the activecell state, it stops monitoring the dormant-CORESET and monitors thenominal CORESETs configured for its active state. As shown in FIG. 21Aand FIG. 21B, after the appropriate switch to activate cell state andmonitoring appropriate BWP, then subsequently receiving the grants onthe activated SCell (step 323 and step 333 for each FIG. 21A and FIG.21B).

Similarly, the UE may switch a cell from dormant state to deactivationstate using the following procedure. The cell-deactivation indicationthrough L1 signaling or higher layer signaling. First, UE may monitorthe dormant-BWP for cell-deactivation indication, wherein the indicationoccurs through L1 signaling such as deactivation-RS or DCI. UE may alsomonitor PCell or PSCell for the cell-deactivation indication; here thedeactivation-indication may occur through L1 or higher layer signaling.Second, when the UE receives the cell-deactivation indication, it mayswitch to the deactivated state. The UE stops monitoring RS and PDCCH inthe dormant-BWP and deactivates the cell.

A single activation-indication or deactivation-indication may impactmultiple SCells. For example, S SCells may be activated or deactivatedthrough a single DCI or a MAC CE. The gNB configures these S cell IDs tothe UE through RRC signaling. The UE may respond to an activation ordeactivation command that received on a DCI through a MAC CE basedacknowledgement which may be sent on an active cell, such as the PCellor PSCell.

A UE may change it monitoring of a cell from active state to dormantstate when it receives an indication (which may be through RRC signalingor MA CE or DCI) on the cell itself or on a PCell or PSCell.Alternatively, a timer ‘active TodormancyTimer’ may be used to determinewhen a cell must switch from active to the dormant state. When the SCellis in the active state for the UE, the UE may set the‘activeTodormancyTimer’ under one or more of the following conditionswhich indicate potential need for resources on the cell: 1) UE transmitsRACH; 2) UE transmits SR; 3) UE transmits scheduled PUSCH; 4) UEtransmits CG PUSCH; 5) UE transmits PUCCH; 6) UE transmits SRS; 7) UEreceives UE-specific grant; or 8) UE receives PDSCH.

When the timer expires, the UE may switch to the dormant state. Theprocedure is illustrated in FIG. 22. At step 341, the active BWP of theactive SCell may be monitored. At step 342, determine whether there is agrant for SCell from gNB. Proceed to step 341 (B) if no grant andproceed to step 343 if there is a grant. At step 343,activetoDorancyTimer may be set. At step 344, determine whetheractiveToDormancyTimer has expired. Proceed to step 346 if not expiredand proceed to step 345 if expired. At step 345, based on the expiringof the timer, then there may be a move of SCell to dormant state.Alternatively, at step 346, if no expiration of the timer then decrementand proceed back to step 344.

A timer ‘dormantToDeactiveTimer’ may be used to determine when a cellmust switch from dormant to deactivated state. The UE may set this timerwhen it enters the dormant state. Alternatively, the UE may receive anindication from the gNB to start the timer on the same SCell or thePCell or PSCell. On receiving this indication, the UE starts this timer.When the timer expires, the UE may deactivate the cell. This procedureis shown in FIG. 23. At step 351, dormant state is entered anddormantToDeactivateTimer may be set. At step 353, there is adetermination of whether dormantToDeactivateTimer is expired. Ifexpired, then move SCell to deactivated state as provided in step 353.If not expired, then decrement dormantToDeactivateTimer as provided instep 354. Subsequent to decrement, UE may proceed back to step 352.

If the UE receives a cell-activation indication during the dormantstate, the UE may suspend (e.g., freeze) dormantToDeactiveTimer andactivates the cell.

SCell procedures for power savings—Bundled behavior on PCell/PSCell andSCells: If a UE sleeps on an SCell at the same time that it sleeps onthe PCell, it can optimize its power saving by ramping down variousRx-Tx and digital operations in the modem. So it may be advantageous tosynchronize the UE's power states between the PCell and SCells to thepossible extent.

Also, for use cases with bursty traffic, the SCells supplement the PCellor PSCell with more resources. If the UE is unlikely to receive ortransmit on the PCell or PSCell, then it is unlikely to receive ortransmit on the SCells. So, the SCells may be bundled in a way that ifthe power savings signal is received in one cell, then it may impact thebehavior on S SCells. Or, certain UE behavior on one cell influences theUE behavior on the cells in the bundle.

The concept of bundling is shown in FIG. 24 where the UE's PCell isbundled with some SCells and PSCell is bundled with some SCells.

A correspondence between PSCs of the bundled cells may define thebehavior of the bundled cells. For example, as shown in FIG. 25, a PSCon PCell may correspond to a PSC in the SCell. If PSC_(P,1) of PCell isactivated, then PSC_(S,1) of SCell is automatically activated.

A single cell may also be present in multiple bundles as shown in theexample in FIG. 26. Here the PCell is part of two bundles. At a time onebundle may be active—so, the SCells in that bundle may be influenced bythe signaling or behavior in the PCell. For example, if bundle #1 isactive, UE may micro-sleep in SCell₁ and SCell₂ when it micro-sleeps inthe PCell.

An active bundle may be configured through RRC signaling or provisionedthrough a MAC CE through L1 signaling such as the power savings signal.

Any PSC activation or PSC deactivation or micro-sleep behavior in a cellmay trigger corresponding activation, deactivation or micro-sleepbehavior in all cells in the active bundle. Optionally, a leader may bedefined for a bundle; so activation or deactivation or micro-sleepbehavior on the leader cell alone automatically triggers PSC activation,PSC deactivation, or micro-sleep behavior in the active bundle.

A wake-up signal or sleep signal on one Cell may indicate the UE to wakeup or sleep on another cell. For example, a wake-up on the PCell mayindicate the UE to wake-up on its PCell and S of its N configuredSCells. Alternatively, a wake-up signal on the PCell may indicate the UEto wake-up on its PCell from micro-sleep and activate S of its Nconfigured SCells from the dormant state.

A go-to-sleep signal on the PCell may indicate the UE to micro-sleep onthe PCell and micro-sleep on S of its N SCells for certain duration suchas D DRX cycles. Alternatively, a go-to-sleep signal on the PCell mayindicate the UE to micro-sleep on the PCell for certain duration such asD DRX cycles and switch to the dormant state on S of its N SCells.

The wake-up signal or go-to-sleep signal may also indicate the specificbundle (of S) SCells that must react to the power savings procedure. Thebundles, indexed in a table, may be configured through RRC. An indexinto this table may be provided by the power savings signal to indicatethe activated bundle.

If the power savings signal is in the form of a BWP activation DCI, aBWP switch in one cell may automatically trigger a BWP switch on bundledcells. For example, a BWP switch in the PCell from BWP_(P,1) orBWP_(P,2) may trigger a BWP switch from BWP_(S,1) or BWP_(S,2) on thebundled SCell as shown in FIG. 27.

If a UE's BWPInactivityTimer expires on the PCell, the UE switches tothe default BWP on the PCell. This switch may also trigger the UE toswitch to the default BWP on a bundled SCell after completing ascheduled transmission on the SCell, even if the SCell'sBWPInactivityTimer has not expired.

Alternatively, when a UE may switch to the default BWP in a Cell such asthe PCell, the UE may go to the dormant state in the bundled SCells.

If a CORESET or search space is activated or deactivated for one cell, acorresponding CORESET or search space may be activated or deactivatedfor the bundled cells.

In general, a power savings signal received on an SCell may also impactthe micro-sleep behavior on a PCell or PSCell or another SCell. And thesolutions discussed above may also apply to this scenario.

SCell procedures for power savings—UE-assisted SCell activation: When aUE has data to send, it may activate S SCells. A sample procedure isdescribed below and illustrated in FIG. 28. At step 361, when UE 99sends an SR (which may be on a PCell or SCell), it activates a bundlewhich may have been in the dormant state. The bundle may be autonomouslyselected by UE 99 or configured by the gNB 98. At step 362, gNB 98 mayprovide a UL grant. At step 363, UE 99 may feedback the activated bundleto gNB 98. This indication may be sent along with the UE's BSR. If gNB98 does not schedule UE 99 on a cell (from the activated bundle) within‘activeTodormancyTimer’ expiration, UE 99 may return that cell to thedormant state. At step 364, gNB 98 may provide schedule for UL.

If UE 99 has the option to choose from multiple bundles, it may select abundle based on the amount of data to be transmitted, for example, itsBSR. Larger BSR may imply activating a bundle with more cells or cellswith larger bandwidth.

The PDCCH based power savings signal may include one or more of thefollowing fields in its DCI, as shown in Table 4.

TABLE 4 Fields Description Wake-up-indicator Wake Up IndicationGTS-indicator Go to sleep indication BWP-indicator BWP to switch to onreceiving Wake-up or GTS indication PSC-indicator Power savingconfiguration to use for PCell and PSCell and SCells TDRA-indicator TDRAtable to be used SCell-activation Activate/deactivate one or more SCellsSearch-space- Indicate parameters to change indication the monitoringperiodicity

FIG. 39 illustrates exemplary fields and locations of the fields withinthe DCI. Not all fields may be present for each UE. The applicablefields in a DCI may be configured to the UE through RRC signaling. It iscontemplated that a single DCI may carry the power savings instructionto multiple UEs. In this case, the location of the fields within a DCIfor a UE may also be indicated through RRC signaling as shown in theexample in FIG. 39. Here UE1, UE2 have a common ‘field1’ while only UE1is configured to receive ‘field2’. For example, UEs that do have SCellsneed not receive fields related to SCell activation.

As a special case, a GTS PDCCH may be a signal to provide only a singlebit of information to each UE through a common DCI. Here, each bit inthe DCI payload may correspond to one UE. The location of the bit in thebitmap may be configured to the UE; so the UE may look for the bot inthat location to decide if it has received an instruction to sleep.

Power savings in the IDLE or INACTIVE state—UE specific paging DCI. Inorder to avoid false alarm, a UE may be paged by a UE-specific DCI. Inthe IDLE or INACTIVE state, the DCI may use an IDLE/INACTIVE-ID toscramble the DCI. The II-ID may be derived from the UE's ID such as theIMSI or TMSI by masking some of the bits in IMSI or TMSI. This reducesfalse paging alarm but does not fully eliminate it as multiple UEs canhave the same II-ID even if their IMSI/TMSI are unique. The DCI maycarry in the payload, the masked bits of the UE's identity as shown inFIG. 29. Together with the II-ID and DCI payload, the UE may recognizeif it has been paged. The UE need not decode a PDSCH to determine if ithas been paged. This provides some power savings.

As paging DCIs are UE-specific, the resources for control signaling maybe significant for the gNB and may block other PDCCHs in the CORESET. Sothis method may be suitable for cells with few UEs and low traffic load.For example, a sensor deployment in a small cell may be configured forsuch operation. However, for flexibility, the gNB may switch the type ofpaging to adapt to the ongoing traffic. The gNB may indicate the type ofpaging used, e.g., UE-specific paging or legacy (broadcast) pagingmethod through SI such as the MIB or RMSI.

The gNB may also support a specific paging method for certain use cases.For example, for URLLC UEs, the gNB may provide UE-specific paging toenable low latency operation. For mMTC UEs, the gNB may provideUE-specific paging to avoid false paging alarms. Whereas for eMBB UEs,the gNB may still employ legacy paging. Enough context about the UE maybe stored in the network to enable a suitable paging method for a givenUE.

The UE-specific paging DCI need not provide PDSCH allocation. However,for some case, it is advantageous to support grant provision though theUE-specific paging DCI. For example, a URLLC UE may receive a DL or ULgrant in the UE-specific paging DCI as shown in FIG. 30.

For some use cases, it may be beneficial to support both broadcast andUE-specific paging. If a UE supports both URLLC and eMBB traffic, it maybe paged through one or the other method. UE-specific DCI with a grantmay be provided for URLLC traffic. Legacy paging may be used for eMBBtraffic. So the UE may monitor both types of paging DCIs. The monitoringoccasions may be configured independently for each paging type.

Power savings in the IDLE or INACTIVE state—Configuring MultiplePaging-RNTIs (P-RNTI). The gNB may configure multiple P-RNTIs in anetwork. They may be available through the SI, such as RMSI or OSI. Ahash function may map a UE's ID such as IMSI or TMSI to N Paging RNTIs(denoted by P₁-RNTI, P₂-RNTI, . . . P_(N)-RNTI). Then the UE may monitorpaging indication only on the paging RNTIs corresponding to its ID. Asthe gNB splits the UEs across different RNTIs, number of false pagingalarms per UE can be reduced. The UE still has to decode the pagingPDSCH to detect if its UE ID is resent to determine if it has beenpaged. FIG. 31 UE may monitor R1-RNTI, P2-RNTI, or P4-RNTI out of thepool of paging RNTIs.

Power savings in the IDLE or INACTIVE state—Using a Wake-up signal forpaging: A wake-up signal may be used to indicate whether or not a UEshould monitor during a paging occasion. This may reduce excessivemonitoring during the paging occasions. The wake-up signal may be in theform of an OOK signal or an RS or DCI in the common search space. Whenthe UE detects the wake-up signal, it monitors the paging DCI in thefollowing paging occasion. If it does not detect the wake-up signal, itneed not monitor the following paging occasion.

The wake-up signal configurations may be provided through the RMSI orOSI. For example, multiple OOK configurations may be broadcasted. A UE'sID may map to one or more OOK signals. Then the UE may monitor thosespecific OOK signals for indication of wake-up signaling for paging.

It is understood that the entities performing the steps illustratedherein may be logical entities. The steps may be stored in a memory of,and executing on a processor of, a device, server, or computer systemsuch as those illustrated in FIG. 21-FIG. 23, or FIG. 28, among others.Skipping steps, combining steps, or adding steps between exemplarymethods disclosed herein is contemplated. Table 4 provides exampleabbreviations and definitions.

TABLE 5 Abbreviations and Definitions Abbreviations Definitions ALAggregation Level BWP Bandwidth Part CDRX Connected Mode DiscontinuousReception C-RNTI Cell Radio-Network Temporary Identifier CSI-RS ChannelState Information Reference Signal DCI Downlink Control Information DLDownlink DRX Discontinuous Reception eMBB enhanced Mobile Broadband FDDFrequency Division Duplex gNB NR NodeB GTS Go-to-Sleep IE InformationElement L1 Layer-1 LTE Long Term Evolution MAC Medium Access Control MIBMaster Information Block NB NodeB NR New Radio OFDM Orthogonal FrequencyDivision Multiplexing OOK On-Off Keying OSI Other System InformationPDCCH Physical Downlink Control CHannel PHY Physical Layer POWPre-OnDuration-Window PRACH Physical Random Access Channel PSC PowerSavings Configuration RACH Random Access Channel RAN Radio AccessNetwork RMSI Remaining System Information RNTI Radio Network TemporaryIdentification RRC Radio Resource Control SFI Slot format Indicator SISystem Information SLIV Start and Length Indicator Value SR SchedulingRequest TDD Time Division Duplex TDRA Time Domain Resource AllocationTRS Tracking Reference Signal TTI Transmission Time Interval UE UserEquipment UL Uplink

FIG. 11 and FIG. 33 illustrate exemplary displays (e.g., graphical userinterface) that may be generated based on the methods, systems, anddevices of power saving in NR, as discussed herein. Display interface901 (e.g., touch screen display) may provide text in block 902associated with of power saving in NR, such as RRC related parameters,monitoring PDCCH for the wake-up trigger, and other power saving methodflows, among other things. Progress of any of the steps (e.g., sentmessages or success of steps) discussed herein may be displayed withoutput 902 or output 903. In addition, graphical output 902 or output903 may be displayed on display interface 901. Graphical output may bethe topology of the devices implementing the methods, systems, anddevices of power saving in NR, a graphical output of the progress of anymethod or systems discussed herein, or the like.

The 3rd Generation Partnership Project (3GPP) develops technicalstandards for cellular telecommunications network technologies,including radio access, the core transport network, and servicecapabilities—including work on codecs, security, and quality of service.Recent radio access technology (RAT) standards include WCDMA (commonlyreferred as 3G), LTE (commonly referred as 4G), LTE-Advanced standards,and New Radio (NR), which is also referred to as “5G”. 3GPP NR standardsdevelopment is expected to continue and include the definition of nextgeneration radio access technology (new RAT), which is expected toinclude the provision of new flexible radio access below 7 GHz, and theprovision of new ultra-mobile broadband radio access above 7 GHz. Theflexible radio access is expected to consist of a new, non-backwardscompatible radio access in new spectrum below 6 GHz, and it is expectedto include different operating modes that may be multiplexed together inthe same spectrum to address a broad set of 3GPP NR use cases withdiverging requirements. The ultra-mobile broadband is expected toinclude cmWave and mmWave spectrum that will provide the opportunity forultra-mobile broadband access for, e.g., indoor applications andhotspots. In particular, the ultra-mobile broadband is expected to sharea common design framework with the flexible radio access below 7 GHz,with cmWave and mmWave specific design optimizations.

3GPP has identified a variety of use cases that NR is expected tosupport, resulting in a wide variety of user experience requirements fordata rate, latency, and mobility. The use cases include the followinggeneral categories: enhanced mobile broadband (eMBB) ultra-reliablelow-latency Communication (URLLC), massive machine type communications(mMTC), network operation (e.g., network slicing, routing, migration andinterworking, energy savings), and enhanced vehicle-to-everything (eV2X)communications, which may include any of Vehicle-to-VehicleCommunication (V2V), Vehicle-to-Infrastructure Communication (V2I),Vehicle-to-Network Communication (V2N), Vehicle-to-PedestrianCommunication (V2P), and vehicle communications with other entities.Specific service and applications in these categories include, e.g.,monitoring and sensor networks, device remote controlling,bi-directional remote controlling, personal cloud computing, videostreaming, wireless cloud-based office, first responder connectivity,automotive recall, disaster alerts, real-time gaming, multi-person videocalls, autonomous driving, augmented reality, tactile internet, virtualreality, home automation, robotics, and aerial drones to name a few. Allof these use cases and others are contemplated herein.

FIG. 32A illustrates an example communications system 100 in which themethods and apparatuses of power savings in NR, described and claimedherein may be used. The communications system 100 may include wirelesstransmit/receive units (WTRUs) 102 a, 102 b, 102 c, 102 d, 102 e, 102 f,or 102 g (which generally or collectively may be referred to as WTRU 102or WTRUs 102). The communications system 100 may include, a radio accessnetwork (RAN) 103/104/105/103 b/104 b/105 b, a core network 106/107/109,a public switched telephone network (PSTN) 108, the Internet 110, othernetworks 112, and Network Services 113. Network Services 113 mayinclude, for example, a V2X server, V2X functions, a ProSe server, ProSefunctions, IoT services, video streaming, or edge computing, etc.

It will be appreciated that the concepts disclosed herein may be usedwith any number of WTRUs, base stations, networks, or network elements.Each of the WTRUs 102 a, 102 b, 102 c, 102 d, 102 e, 102 f, or 102 g maybe any type of apparatus or device configured to operate or communicatein a wireless environment. Although each WTRU 102 a, 102 b, 102 c, 102d, 102 e, 102 f, or 102 g may be depicted in FIG. 32A, FIG. 32B, FIG.32C, FIG. 32D, FIG. 32E, or FIG. 32F as a hand-held wirelesscommunications apparatus, it is understood that with the wide variety ofuse cases contemplated for 5G wireless communications, each WTRU maycomprise or be embodied in any type of apparatus or device configured totransmit or receive wireless signals, including, by way of example only,user equipment (UE), a mobile station, a fixed or mobile subscriberunit, a pager, a cellular telephone, a personal digital assistant (PDA),a smartphone, a laptop, a tablet, a netbook, a notebook computer, apersonal computer, a wireless sensor, consumer electronics, a wearabledevice such as a smart watch or smart clothing, a medical or eHealthdevice, a robot, industrial equipment, a drone, a vehicle such as a car,bus, truck, train, or airplane, and the like.

The communications system 100 may also include a base station 114 a anda base station 114 b. In the example of FIG. 32A, each base stations 114a and 114 b is depicted as a single element. In practice, the basestations 114 a and 114 b may include any number of interconnected basestations or network elements. Base stations 114 a may be any type ofdevice configured to wirelessly interface with at least one of the WTRUs102 a, 102 b, and 102 c to facilitate access to one or morecommunication networks, such as the core network 106/107/109, theInternet 110, Network Services 113, or the other networks 112.Similarly, base station 114 b may be any type of device configured towiredly or wirelessly interface with at least one of the Remote RadioHeads (RRHs) 118 a, 118 b, Transmission and Reception Points (TRPs) 119a, 119 b, or Roadside Units (RSUs) 120 a and 120 b to facilitate accessto one or more communication networks, such as the core network106/107/109, the Internet 110, other networks 112, or Network Services113. RRHs 118 a, 118 b may be any type of device configured towirelessly interface with at least one of the WTRUs 102, e.g., WTRU 102c, to facilitate access to one or more communication networks, such asthe core network 106/107/109, the Internet 110, Network Services 113, orother networks 112

TRPs 119 a, 119 b may be any type of device configured to wirelesslyinterface with at least one of the WTRU 102 d, to facilitate access toone or more communication networks, such as the core network106/107/109, the Internet 110, Network Services 113, or other networks112. RSUs 120 a and 120 b may be any type of device configured towirelessly interface with at least one of the WTRU 102 e or 102 f, tofacilitate access to one or more communication networks, such as thecore network 106/107/109, the Internet 110, other networks 112, orNetwork Services 113. By way of example, the base stations 114 a, 114 bmay be a Base Transceiver Station (BTS), a Node-B, an eNode B, a HomeNode B, a Home eNode B, a Next Generation Node-B (gNode B), a satellite,a site controller, an access point (AP), a wireless router, and thelike.

The base station 114 a may be part of the RAN 103/104/105, which mayalso include other base stations or network elements (not shown), suchas a Base Station Controller (BSC), a Radio Network Controller (RNC),relay nodes, etc. Similarly, the base station 114 b may be part of theRAN 103 b/104 b/105 b, which may also include other base stations ornetwork elements (not shown), such as a BSC, a RNC, relay nodes, etc.The base station 114 a may be configured to transmit or receive wirelesssignals within a particular geographic region, which may be referred toas a cell (not shown). Similarly, the base station 114 b may beconfigured to transmit or receive wired or wireless signals within aparticular geographic region, which may be referred to as a cell (notshown) for methods, systems, and devices of power saving in NR, asdisclosed herein. Similarly, the base station 114 b may be configured totransmit or receive wired or wireless signals within a particulargeographic region, which may be referred to as a cell (not shown). Thecell may further be divided into cell sectors. For example, the cellassociated with the base station 114 a may be divided into threesectors. Thus, in an example, the base station 114 a may include threetransceivers, e.g., one for each sector of the cell. In an example, thebase station 114 a may employ multiple-input multiple output (MIMO)technology and, therefore, may utilize multiple transceivers for eachsector of the cell.

The base stations 114 a may communicate with one or more of the WTRUs102 a, 102 b, 102 c, or 102 g over an air interface 115/116/117, whichmay be any suitable wireless communication link (e.g., radio frequency(RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave,mmWave, etc.). The air interface 115/116/117 may be established usingany suitable radio access technology (RAT).

The base stations 114 b may communicate with one or more of the RRHs 118a, 118 b, TRPs 119 a, 119 b, or RSUs 120 a, 120 b, over a wired or airinterface 115 b/116 b/117 b, which may be any suitable wired (e.g.,cable, optical fiber, etc.) or wireless communication link (e.g., radiofrequency (RF), microwave, infrared (IR), ultraviolet (UV), visiblelight, cmWave, mmWave, etc.). The air interface 115 b/116 b/117 b may beestablished using any suitable radio access technology (RAT).

The RRHs 118 a, 118 b, TRPs 119 a, 119 b or RSUs 120 a, 120 b, maycommunicate with one or more of the WTRUs 102 c, 102 d, 102 e, 102 fover an air interface 115 c/116 c/117 c, which may be any suitablewireless communication link (e.g., radio frequency (RF), microwave,infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.).The air interface 115 c/116 c/117 c may be established using anysuitable radio access technology (RAT).

The WTRUs 102 a, 102 b, 102 c,102 d, 102 e, or 102 f may communicatewith one another over an air interface 115 d/116 d/117 d, such asSidelink communication, which may be any suitable wireless communicationlink (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet(UV), visible light, cmWave, mmWave, etc.). The air interface 115 d/116d/117 d may be established using any suitable radio access technology(RAT).

The communications system 100 may be a multiple access system and mayemploy one or more channel access schemes, such as CDMA, TDMA, FDMA,OFDMA, SC-FDMA, and the like. For example, the base station 114 a in theRAN 103/104/105 and the WTRUs 102 a, 102 b, 102 c, or RRHs 118 a, 118b,TRPs 119 a, 119 b and RSUs 120 a, 120 b, in the RAN 103 b/104 b/105 band the WTRUs 102 c, 102 d, 102 e, 102 f, may implement a radiotechnology such as Universal Mobile Telecommunications System (UMTS)Terrestrial Radio Access (UTRA), which may establish the air interface115/116/117 or 115 c/116 c/117 c respectively using wideband CDMA(WCDMA). WCDMA may include communication protocols such as High-SpeedPacket Access (HSPA) or Evolved HSPA (HSPA+). HSPA may includeHigh-Speed Downlink Packet Access (HSDPA) or High-Speed Uplink PacketAccess (HSUPA).

In an example, the base station 114 a and the WTRUs 102 a, 102 b, 102 c,or RRHs 118 a, 118 b, TRPs 119 a, 119 b, or RSUs 120 a, 120 b in the RAN103 b/104 b/105 b and the WTRUs 102 c, 102 d, may implement a radiotechnology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), whichmay establish the air interface 115/116/117 or 115 c/116 c/117 crespectively using Long Term Evolution (LTE) or LTE-Advanced (LTE-A). Inthe future, the air interface 115/116/117 or 115 c/116 c/117 c mayimplement 3GPP NR technology. The LTE and LTE-A technology may includeLTE D2D and V2X technologies and interfaces (such as Sidelinkcommunications, etc.). Similarly, the 3GPP NR technology includes NR V2Xtechnologies and interface (such as Sidelink communications, etc.).

The base station 114 a in the RAN 103/104/105 and the WTRUs 102 a, 102b, 102 c, and 102 g or RRHs 118 a, 118 b, TRPs 119 a, 119 b or RSUs 120a, 120 b in the RAN 103 b/104 b/105 b and the WTRUs 102 c, 102 d, 102 e,102 f may implement radio technologies such as IEEE 802.16 (e.g.,Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000,CDMA2000 1×, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), InterimStandard 95 (IS-95), Interim Standard 856 (IS-856), Global System forMobile communications (GSM), Enhanced Data rates for GSM Evolution(EDGE), GSM EDGE (GERAN), and the like.

The base station 114 c in FIG. 32A may be a wireless router, Home NodeB, Home eNode B, or access point, for example, and may utilize anysuitable RAT for facilitating wireless connectivity in a localized area,such as a place of business, a home, a vehicle, a train, an aerial, asatellite, a manufactory, a campus, and the like, for implementing themethods, systems, and devices of power saving in NR, as disclosedherein. In an example, the base station 114 c and the WTRUs 102, e.g.,WTRU 102 e, may implement a radio technology such as IEEE 802.11 toestablish a wireless local area network (WLAN). similarly, the basestation 114 c and the WTRUs 102 d, may implement a radio technology suchas IEEE 802.15 to establish a wireless personal area network (WPAN). Inyet another example, the base station 114 c and the WTRUs 102, e.g.,WTRU 102 e, may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000,GSM, LTE, LTE-A, NR, etc.) to establish a picocell or femtocell. Asshown in FIG. 32A, the base station 114 c may have a direct connectionto the Internet 110. Thus, the base station 114 c may not be required toaccess the Internet 110 via the core network 106/107/109.

The RAN 103/104/105 or RAN 103 b/104 b/105 b may be in communicationwith the core network 106/107/109, which may be any type of networkconfigured to provide voice, data, messaging, authorization andauthentication, applications, or voice over internet protocol (VoIP)services to one or more of the WTRUs 102 a, 102 b, 102 c, 102 d. Forexample, the core network 106/107/109 may provide call control, billingservices, mobile location-based services, pre-paid calling, Internetconnectivity, packet data network connectivity, Ethernet connectivity,video distribution, etc., or perform high-level security functions, suchas user authentication.

Although not shown in FIG. 32A, it will be appreciated that the RAN103/104/105 or RAN 103 b/104 b/105 b or the core network 106/107/109 maybe in direct or indirect communication with other RANs that employ thesame RAT as the RAN 103/104/105 or RAN 103 b/104 b/105 b or a differentRAT. For example, in addition to being connected to the RAN 103/104/105or RAN 103 b/104 b/105 b, which may be utilizing an E-UTRA radiotechnology, the core network 106/107/109 may also be in communicationwith another RAN (not shown) employing a GSM or NR radio technology.

The core network 106/107/109 may also serve as a gateway for the WTRUs102 a, 102 b, 102 c, 102 d, 102 e to access the PSTN 108, the Internet110, or other networks 112. The PSTN 108 may include circuit-switchedtelephone networks that provide plain old telephone service (POTS). TheInternet 110 may include a global system of interconnected computernetworks and devices that use common communication protocols, such asthe transmission control protocol (TCP), user datagram protocol (UDP)and the internet protocol (IP) in the TCP/IP internet protocol suite.The networks 112 may include wired or wireless communications networksowned or operated by other service providers. For example, the networks112 may include any type of packet data network (e.g., an IEEE 802.3Ethernet network) or another core network connected to one or more RANs,which may employ the same RAT as the RAN 103/104/105 or RAN 103 b/104b/105 b or a different RAT.

Some or all of the WTRUs 102 a, 102 b, 102 c, 102 d, 102 e, and 102 f inthe communications system 100 may include multi-mode capabilities, e.g.,the WTRUs 102 a, 102 b, 102 c, 102 d, 102 e, and 102 f may includemultiple transceivers for communicating with different wireless networksover different wireless links for implementing methods, systems, anddevices of power saving in NR, as disclosed herein. For example, theWTRU 102 g shown in FIG. 32A may be configured to communicate with thebase station 114 a, which may employ a cellular-based radio technology,and with the base station 114 c, which may employ an IEEE 802 radiotechnology.

Although not shown in FIG. 32A, it will be appreciated that a UserEquipment may make a wired connection to a gateway. The gateway maybe aResidential Gateway (RG). The RG may provide connectivity to a CoreNetwork 106/107/109. It will be appreciated that many of the ideasincluded herein may equally apply to UEs that are WTRUs and UEs that usea wired connection to connect to a network. For example, the ideas thatapply to the wireless interfaces 115, 116, 117 and 115 c/116 c/117 c mayequally apply to a wired connection.

FIG. 32B is a system diagram of an example RAN 103 and core network 106that may implement methods, systems, and devices of power saving in NR,as disclosed herein. As noted above, the RAN 103 may employ a UTRA radiotechnology to communicate with the WTRUs 102 a, 102 b, and 102 c overthe air interface 115. The RAN 103 may also be in communication with thecore network 106. As shown in FIG. 32B, the RAN 103 may include Node-Bs140 a, 140 b, and 140 c, which may each include one or more transceiversfor communicating with the WTRUs 102 a, 102 b, and 102 c over the airinterface 115. The Node-Bs 140 a, 140 b, and 140 c may each beassociated with a particular cell (not shown) within the RAN 103. TheRAN 103 may also include RNCs 142 a, 142 b. It will be appreciated thatthe RAN 103 may include any number of Node-Bs and Radio NetworkControllers (RNCs.)

As shown in FIG. 32B, the Node-Bs 140 a, 140 b may be in communicationwith the RNC 142 a. Additionally, the Node-B 140 c may be incommunication with the RNC 142 b. The Node-Bs 140 a, 140 b, and 140 cmay communicate with the respective RNCs 142 a and 142 b via an Iubinterface. The RNCs 142 a and 142 b may be in communication with oneanother via an Iur interface. Each of the RNCs 142 a and 142 b may beconfigured to control the respective Node-Bs 140 a, 140 b, and 140 c towhich it is connected. In addition, each of the RNCs 142 a and 142 b maybe configured to carry out or support other functionality, such as outerloop power control, load control, admission control, packet scheduling,handover control, macro-diversity, security functions, data encryption,and the like.

The core network 106 shown in FIG. 32B may include a media gateway (MGW)144, a Mobile Switching Center (MSC) 146, a Serving GPRS Support Node(SGSN) 148, or a Gateway GPRS Support Node (GGSN) 150. While each of theforegoing elements are depicted as part of the core network 106, it willbe appreciated that any one of these elements may be owned or operatedby an entity other than the core network operator.

The RNC 142 a in the RAN 103 may be connected to the MSC 146 in the corenetwork 106 via an IuCS interface. The MSC 146 may be connected to theMGW 144. The MSC 146 and the MGW 144 may provide the WTRUs 102 a, 102 b,and 102 c with access to circuit-switched networks, such as the PSTN108, to facilitate communications between the WTRUs 102 a, 102 b, and102 c, and traditional land-line communications devices.

The RNC 142 a in the RAN 103 may also be connected to the SGSN 148 inthe core network 106 via an IuPS interface. The SGSN 148 may beconnected to the GGSN 150. The SGSN 148 and the GGSN 150 may provide theWTRUs 102 a, 102 b, and 102 c with access to packet-switched networks,such as the Internet 110, to facilitate communications between and theWTRUs 102 a, 102 b, and 102 c, and IP-enabled devices.

The core network 106 may also be connected to the other networks 112,which may include other wired or wireless networks that are owned oroperated by other service providers.

FIG. 32C is a system diagram of an example RAN 104 and core network 107that may implement methods, systems, and devices of power saving in NR,as disclosed herein. As noted above, the RAN 104 may employ an E-UTRAradio technology to communicate with the WTRUs 102 a, 102 b, and 102 cover the air interface 116. The RAN 104 may also be in communicationwith the core network 107.

The RAN 104 may include eNode-Bs 160 a, 160 b, and 160 c, though it willbe appreciated that the RAN 104 may include any number of eNode-Bs. TheeNode-Bs 160 a, 160 b, and 160 c may each include one or moretransceivers for communicating with the WTRUs 102 a, 102 b, and 102 cover the air interface 116. For example, the eNode-Bs 160 a, 160 b, and160 c may implement MIMO technology. Thus, the eNode-B 160 a, forexample, may use multiple antennas to transmit wireless signals to, andreceive wireless signals from, the WTRU 102 a.

Each of the eNode-Bs 160 a, 160 b, and 160 c may be associated with aparticular cell (not shown) and may be configured to handle radioresource management decisions, handover decisions, scheduling of usersin the uplink or downlink, and the like. As shown in FIG. 32C, theeNode-Bs 160 a, 160 b, and 160 c may communicate with one another overan X2 interface.

The core network 107 shown in FIG. 32C may include a Mobility ManagementGateway (MME) 162, a serving gateway 164, and a Packet Data Network(PDN) gateway 166. While each of the foregoing elements are depicted aspart of the core network 107, it will be appreciated that any one ofthese elements may be owned or operated by an entity other than the corenetwork operator.

The MME 162 may be connected to each of the eNode-Bs 160 a, 160 b, and160 c in the RAN 104 via an S1 interface and may serve as a controlnode. For example, the MME 162 may be responsible for authenticatingusers of the WTRUs 102 a, 102 b, and 102 c, beareractivation/deactivation, selecting a particular serving gateway duringan initial attach of the WTRUs 102 a, 102 b, and 102 c, and the like.The MME 162 may also provide a control plane function for switchingbetween the RAN 104 and other RANs (not shown) that employ other radiotechnologies, such as GSM or WCDMA.

The serving gateway 164 may be connected to each of the eNode-Bs 160 a,160 b, and 160 c in the RAN 104 via the S1 interface. The servinggateway 164 may generally route and forward user data packets to/fromthe WTRUs 102 a, 102 b, and 102 c. The serving gateway 164 may alsoperform other functions, such as anchoring user planes duringinter-eNode B handovers, triggering paging when downlink data isavailable for the WTRUs 102 a, 102 b, and 102 c, managing and storingcontexts of the WTRUs 102 a, 102 b, and 102 c, and the like.

The serving gateway 164 may also be connected to the PDN gateway 166,which may provide the WTRUs 102 a, 102 b, and 102 c with access topacket-switched networks, such as the Internet 110, to facilitatecommunications between the WTRUs 102 a, 102 b, 102 c, and IP-enableddevices.

The core network 107 may facilitate communications with other networks.For example, the core network 107 may provide the WTRUs 102 a, 102 b,and 102 c with access to circuit-switched networks, such as the PSTN108, to facilitate communications between the WTRUs 102 a, 102 b, and102 c and traditional land-line communications devices. For example, thecore network 107 may include, or may communicate with, an IP gateway(e.g., an IP Multimedia Subsystem (IMS) server) that serves as aninterface between the core network 107 and the PSTN 108. In addition,the core network 107 may provide the WTRUs 102 a, 102 b, and 102 c withaccess to the networks 112, which may include other wired or wirelessnetworks that are owned or operated by other service providers.

FIG. 32D is a system diagram of an example RAN 105 and core network 109that may implement methods, systems, and devices of power saving in NR,as disclosed herein. The RAN 105 may employ an NR radio technology tocommunicate with the WTRUs 102 a and 102 b over the air interface 117.The RAN 105 may also be in communication with the core network 109. ANon-3GPP Interworking Function (N3IWF) 199 may employ a non-3GPP radiotechnology to communicate with the WTRU 102 c over the air interface198. The N3IWF 199 may also be in communication with the core network109.

The RAN 105 may include gNode-Bs 180 a and 180 b. It will be appreciatedthat the RAN 105 may include any number of gNode-Bs. The gNode-Bs 180 aand 180 b may each include one or more transceivers for communicatingwith the WTRUs 102 a and 102 b over the air interface 117. Whenintegrated access and backhaul connection are used, the same airinterface may be used between the WTRUs and gNode-Bs, which may be thecore network 109 via one or multiple gNBs. The gNode-Bs 180 a and 180 bmay implement MIMO, MU-MIMO, or digital beamforming technology. Thus,the gNode-B 180 a, for example, may use multiple antennas to transmitwireless signals to, and receive wireless signals from, the WTRU 102 a.It should be appreciated that the RAN 105 may employ of other types ofbase stations such as an eNode-B. It will also be appreciated the RAN105 may employ more than one type of base station. For example, the RANmay employ eNode-Bs and gNode-Bs.

The N3IWF 199 may include a non-3GPP Access Point 180 c. It will beappreciated that the N3IWF 199 may include any number of non-3GPP AccessPoints. The non-3GPP Access Point 180 c may include one or moretransceivers for communicating with the WTRUs 102 c over the airinterface 198. The non-3GPP Access Point 180 c may use the 802.11protocol to communicate with the WTRU 102 c over the air interface 198.

Each of the gNode-Bs 180 a and 180 b may be associated with a particularcell (not shown) and may be configured to handle radio resourcemanagement decisions, handover decisions, scheduling of users in theuplink or downlink, and the like. As shown in FIG. 32D, the gNode-Bs 180a and 180 b may communicate with one another over an Xn interface, forexample.

The core network 109 shown in FIG. 32D may be a 5G core network (5GC).The core network 109 may offer numerous communication services tocustomers who are interconnected by the radio access network. The corenetwork 109 comprises a number of entities that perform thefunctionality of the core network. As used herein, the term “corenetwork entity” or “network function” refers to any entity that performsone or more functionalities of a core network. It is understood thatsuch core network entities may be logical entities that are implementedin the form of computer-executable instructions (software) stored in amemory of, and executing on a processor of, an apparatus configured forwireless or network communications or a computer system, such as system90 illustrated in FIG. 32G.

In the example of FIG. 32D, the 5G Core Network 109 may include anaccess and mobility management function (AMF) 172, a Session ManagementFunction (SMF) 174, User Plane Functions (UPFs) 176 a and 176 b, a UserData Management Function (UDM) 197, an Authentication Server Function(AUSF) 190, a Network Exposure Function (NEF) 196, a Policy ControlFunction (PCF) 184, a Non-3GPP Interworking Function (N3IWF) 199, a UserData Repository (UDR) 178. While each of the foregoing elements aredepicted as part of the 5G core network 109, it will be appreciated thatany one of these elements may be owned or operated by an entity otherthan the core network operator. It will also be appreciated that a 5Gcore network may not consist of all of these elements, may consist ofadditional elements, and may consist of multiple instances of each ofthese elements. FIG. 32D shows that network functions directly connectto one another, however, it should be appreciated that they maycommunicate via routing agents such as a diameter routing agent ormessage buses.

In the example of FIG. 32D, connectivity between network functions isachieved via a set of interfaces, or reference points. It will beappreciated that network functions could be modeled, described, orimplemented as a set of services that are invoked, or called, by othernetwork functions or services. Invocation of a Network Function servicemay be achieved via a direct connection between network functions, anexchange of messaging on a message bus, calling a software function,etc.

The AMF 172 may be connected to the RAN 105 via an N2 interface and mayserve as a control node. For example, the AMF 172 may be responsible forregistration management, connection management, reachability management,access authentication, access authorization. The AMF may be responsibleforwarding user plane tunnel configuration information to the RAN 105via the N2 interface. The AMF 172 may receive the user plane tunnelconfiguration information from the SMF via an N11 interface. The AMF 172may generally route and forward NAS packets to/from the WTRUs 102 a, 102b, and 102 c via an N1 interface. The N1 interface is not shown in FIG.32D.

The SMF 174 may be connected to the AMF 172 via an N11 interface.Similarly the SMF may be connected to the PCF 184 via an N7 interface,and to the UPFs 176 a and 176 b via an N4 interface. The SMF 174 mayserve as a control node. For example, the SMF 174 may be responsible forSession Management, IP address allocation for the WTRUs 102 a, 102 b,and 102 c, management and configuration of traffic steering rules in theUPF 176 a and UPF 176 b, and generation of downlink data notificationsto the AMF 172.

The UPF 176 a and UPF176 b may provide the WTRUs 102 a, 102 b, and 102 cwith access to a Packet Data Network (PDN), such as the Internet 110, tofacilitate communications between the WTRUs 102 a, 102 b, and 102 c andother devices. The UPF 176 a and UPF 176 b may also provide the WTRUs102 a, 102 b, and 102 c with access to other types of packet datanetworks. For example, Other Networks 112 may be Ethernet Networks orany type of network that exchanges packets of data. The UPF 176 a andUPF 176 b may receive traffic steering rules from the SMF 174 via the N4interface. The UPF 176 a and UPF 176 b may provide access to a packetdata network by connecting a packet data network with an N6 interface orby connecting to each other and to other UPFs via an N9 interface. Inaddition to providing access to packet data networks, the UPF 176 may beresponsible packet routing and forwarding, policy rule enforcement,quality of service handling for user plane traffic, downlink packetbuffering.

The AMF 172 may also be connected to the N3IWF 199, for example, via anN2 interface. The N3IWF facilitates a connection between the WTRU 102 cand the 5G core network 170, for example, via radio interfacetechnologies that are not defined by 3GPP. The AMF may interact with theN3IWF 199 in the same, or similar, manner that it interacts with the RAN105.

The PCF 184 may be connected to the SMF 174 via an N7 interface,connected to the AMF 172 via an N15 interface, and to an ApplicationFunction (AF) 188 via an N5 interface. The N15 and N5 interfaces are notshown in FIG. 32D. The PCF 184 may provide policy rules to control planenodes such as the AMF 172 and SMF 174, allowing the control plane nodesto enforce these rules. The PCF 184, may send policies to the AMF 172for the WTRUs 102 a, 102 b, and 102 c so that the AMF may deliver thepolicies to the WTRUs 102 a, 102 b, and 102 c via an N1 interface.Policies may then be enforced, or applied, at the WTRUs 102 a, 102 b,and 102 c.

The UDR 178 may act as a repository for authentication credentials andsubscription information. The UDR may connect to network functions, sothat network function can add to, read from, and modify the data that isin the repository. For example, the UDR 178 may connect to the PCF 184via an N36 interface. Similarly, the UDR 178 may connect to the NEF 196via an N37 interface, and the UDR 178 may connect to the UDM 197 via anN35 interface.

The UDM 197 may serve as an interface between the UDR 178 and othernetwork functions. The UDM 197 may authorize network functions to accessof the UDR 178. For example, the UDM 197 may connect to the AMF 172 viaan N8 interface, the UDM 197 may connect to the SMF 174 via an N10interface. Similarly, the UDM 197 may connect to the AUSF 190 via an N13interface. The UDR 178 and UDM 197 may be tightly integrated.

The AUSF 190 performs authentication related operations and connects tothe UDM 178 via an N13 interface and to the AMF 172 via an N12interface.

The NEF 196 exposes capabilities and services in the 5G core network 109to Application Functions (AF) 188. Exposure may occur on the N33 APIinterface. The NEF may connect to an AF 188 via an N33 interface and itmay connect to other network functions in order to expose thecapabilities and services of the 5G core network 109.

Application Functions 188 may interact with network functions in the 5GCore Network 109. Interaction between the Application Functions 188 andnetwork functions may be via a direct interface or may occur via the NEF196. The Application Functions 188 may be considered part of the 5G CoreNetwork 109 or may be external to the 5G Core Network 109 and deployedby enterprises that have a business relationship with the mobile networkoperator.

Network Slicing is a mechanism that could be used by mobile networkoperators to support one or more ‘virtual’ core networks behind theoperator's air interface. This involves ‘slicing’ the core network intoone or more virtual networks to support different RANs or differentservice types running across a single RAN. Network slicing enables theoperator to create networks customized to provide optimized solutionsfor different market scenarios which demands diverse requirements, e.g.in the areas of functionality, performance and isolation.

3GPP has designed the 5G core network to support Network Slicing.Network Slicing is a good tool that network operators can use to supportthe diverse set of 5G use cases (e.g., massive IoT, criticalcommunications, V2X, and enhanced mobile broadband) which demand verydiverse and sometimes extreme requirements. Without the use of networkslicing techniques, it is likely that the network architecture would notbe flexible and scalable enough to efficiently support a wider range ofuse cases need when each use case has its own specific set ofperformance, scalability, and availability requirements. Furthermore,introduction of new network services should be made more efficient.

Referring again to FIG. 32D, in a network slicing scenario, a WTRU 102a, 102 b, or 102 c may connect to an AMF 172, via an N1 interface. TheAMF may be logically part of one or more slices. The AMF may coordinatethe connection or communication of WTRU 102 a, 102 b, or 102 c with oneor more UPF 176 a and 176 b, SMF 174, and other network functions. Eachof the UPFs 176 a and 176 b, SMF 174, and other network functions may bepart of the same slice or different slices. When they are part ofdifferent slices, they may be isolated from each other in the sense thatthey may utilize different computing resources, security credentials,etc.

The core network 109 may facilitate communications with other networks.For example, the core network 109 may include, or may communicate with,an IP gateway, such as an IP Multimedia Subsystem (IMS) server, thatserves as an interface between the 5G core network 109 and a PSTN 108.For example, the core network 109 may include, or communicate with ashort message service (SMS) service center that facilities communicationvia the short message service. For example, the 5G core network 109 mayfacilitate the exchange of non-IP data packets between the WTRUs 102 a,102 b, and 102 c and servers or applications functions 188. In addition,the core network 170 may provide the WTRUs 102 a, 102 b, and 102 c withaccess to the networks 112, which may include other wired or wirelessnetworks that are owned or operated by other service providers.

The core network entities described herein and illustrated in FIG. 32A,FIG. 32C, FIG. 32D, or FIG. 32E are identified by the names given tothose entities in certain existing 3GPP specifications, but it isunderstood that in the future those entities and functionalities may beidentified by other names and certain entities or functions may becombined in future specifications published by 3GPP, including future3GPP NR specifications. Thus, the particular network entities andfunctionalities described and illustrated in FIG. 32A, FIG. 32B, FIG.32C, FIG. 32D, or FIG. 32E are provided by way of example only, and itis understood that the subject matter disclosed and claimed herein maybe embodied or implemented in any similar communication system, whetherpresently defined or defined in the future.

FIG. 32E illustrates an example communications system 111 in which thesystems, methods, apparatuses that implement power saving in NR,described herein, may be used. Communications system 111 may includeWireless Transmit/Receive Units (WTRUs) A, B, C, D, E, F, a base stationgNB 121, a V2X server 124, and Road Side Units (RSUs) 123 a and 123 b.In practice, the concepts presented herein may be applied to any numberof WTRUs, base station gNBs, V2X networks, or other network elements.One or several or all WTRUs A, B, C, D, E, and F may be out of range ofthe access network coverage 131. WTRUs A, B, and C form a V2X group,among which WTRU A is the group lead and WTRUs B and C are groupmembers.

WTRUs A, B, C, D, E, and F may communicate with each other over a Uuinterface 129 via the gNB 121 if they are within the access networkcoverage 131. In the example of FIG. 32E, WTRUs B and F are shown withinaccess network coverage 131. WTRUs A, B, C, D, E, and F may communicatewith each other directly via a Sidelink interface (e.g., PC5 or NR PC5)such as interface 125 a, 125 b, or 128, whether they are under theaccess network coverage 131 or out of the access network coverage 131.For instance, in the example of FIG. 32E, WRTU D, which is outside ofthe access network coverage 131, communicates with WTRU F, which isinside the coverage 131.

WTRUs A, B, C, D, E, and F may communicate with RSU 123 a or 123 b via aVehicle-to-Network (V2N) 133 or Sidelink interface 125 b. WTRUs A, B, C,D, E, and F may communicate to a V2X Server 124 via aVehicle-to-Infrastructure (V2I) interface 127. WTRUs A, B, C, D, E, andF may communicate to another UE via a Vehicle-to-Person (V2P) interface128.

FIG. 32F is a block diagram of an example apparatus or device WTRU 102that may be configured for wireless communications and operations inaccordance with the systems, methods, and apparatuses that implementpower saving in NR, described herein, such as a WTRU 102 of FIG. 32A,FIG. 32B, FIG. 32C, FIG. 32D, or FIG. 32E, FIG. 21, or FIG. 28 (e.g.,UEs 99 or gNBs 98). As shown in FIG. 32F, the example WTRU 102 mayinclude a processor 118, a transceiver 120, a transmit/receive element122, a speaker/microphone 124, a keypad 126, adisplay/touchpad/indicators 128, non-removable memory 130, removablememory 132, a power source 134, a global positioning system (GPS)chipset 136, and other peripherals 138. It will be appreciated that theWTRU 102 may include any sub-combination of the foregoing elements.Also, the base stations 114 a and 114 b, or the nodes that base stations114 a and 114 b may represent, such as but not limited to transceiverstation (BTS), a Node-B, a site controller, an access point (AP), a homenode-B, an evolved home node-B (eNodeB), a home evolved node-B (HeNB), ahome evolved node-B gateway, a next generation node-B (gNode-B), andproxy nodes, among others, may include some or all of the elementsdepicted in FIG. 32F and may be an exemplary implementation thatperforms the disclosed systems and methods for power saving in NRdescribed herein.

The processor 118 may be a general purpose processor, a special purposeprocessor, a conventional processor, a digital signal processor (DSP), aplurality of microprocessors, one or more microprocessors in associationwith a DSP core, a controller, a microcontroller, Application SpecificIntegrated Circuits (ASICs), Field Programmable Gate Array (FPGAs)circuits, any other type of integrated circuit (IC), a state machine,and the like. The processor 118 may perform signal coding, dataprocessing, power control, input/output processing, or any otherfunctionality that enables the WTRU 102 to operate in a wirelessenvironment. The processor 118 may be coupled to the transceiver 120,which may be coupled to the transmit/receive element 122. While FIG. 32Fdepicts the processor 118 and the transceiver 120 as separatecomponents, it will be appreciated that the processor 118 and thetransceiver 120 may be integrated together in an electronic package orchip.

The transmit/receive element 122 of a UE may be configured to transmitsignals to, or receive signals from, a base station (e.g., the basestation 114 a of FIG. 32A) over the air interface 115/116/117 or anotherUE over the air interface 115 d/116 d/117 d. For example, thetransmit/receive element 122 may be an antenna configured to transmit orreceive RF signals. The transmit/receive element 122 may be anemitter/detector configured to transmit or receive IR, UV, or visiblelight signals, for example. The transmit/receive element 122 may beconfigured to transmit and receive both RF and light signals. It will beappreciated that the transmit/receive element 122 may be configured totransmit or receive any combination of wireless or wired signals.

In addition, although the transmit/receive element 122 is depicted inFIG. 32F as a single element, the WTRU 102 may include any number oftransmit/receive elements 122. More specifically, the WTRU 102 mayemploy MIMO technology. Thus, the WTRU 102 may include two or moretransmit/receive elements 122 (e.g., multiple antennas) for transmittingand receiving wireless signals over the air interface 115/116/117.

The transceiver 120 may be configured to modulate the signals that areto be transmitted by the transmit/receive element 122 and to demodulatethe signals that are received by the transmit/receive element 122. Asnoted above, the WTRU 102 may have multi-mode capabilities. Thus, thetransceiver 120 may include multiple transceivers for enabling the WTRU102 to communicate via multiple RATs, for example NR and IEEE 802.11 orNR and E-UTRA, or to communicate with the same RAT via multiple beams todifferent RRHs, TRPs, RSUs, or nodes.

The processor 118 of the WTRU 102 may be coupled to, and may receiveuser input data from, the speaker/microphone 124, the keypad 126, or thedisplay/touchpad/indicators 128 (e.g., a liquid crystal display (LCD)display unit or organic light-emitting diode (OLED) display unit. Theprocessor 118 may also output user data to the speaker/microphone 124,the keypad 126, or the display/touchpad/indicators 128. In addition, theprocessor 118 may access information from, and store data in, any typeof suitable memory, such as the non-removable memory 130 or theremovable memory 132. The non-removable memory 130 may includerandom-access memory (RAM), read-only memory (ROM), a hard disk, or anyother type of memory storage device. The removable memory 132 mayinclude a subscriber identity module (SIM) card, a memory stick, asecure digital (SD) memory card, and the like. The processor 118 mayaccess information from, and store data in, memory that is notphysically located on the WTRU 102, such as on a server that is hostedin the cloud or in an edge computing platform or in a home computer (notshown). The processor 118 may be configured to control lightingpatterns, images, or colors on the display or indicators 128 in responseto whether the setup of the power saving in NR in some of the examplesdescribed herein are successful or unsuccessful, or otherwise indicate astatus of power saving in NR and associated components. The controllighting patterns, images, or colors on the display or indicators 128may be reflective of the status of any of the method flows or componentsin the FIG.'s illustrated or discussed herein (e.g., FIG. 1-FIG. 31,etc.). Disclosed herein are messages and procedures of power saving inNR. The messages and procedures may be extended to provide interface/APIfor users to request resources via an input source (e.g.,speaker/microphone 124, keypad 126, or display/touchpad/indicators 128)and request, configure, or query power saving in NR related information,among other things that may be displayed on display 128.

The processor 118 may receive power from the power source 134, and maybe configured to distribute or control the power to the other componentsin the WTRU 102. The power source 134 may be any suitable device forpowering the WTRU 102. For example, the power source 134 may include oneor more dry cell batteries, solar cells, fuel cells, and the like.

The processor 118 may also be coupled to the GPS chipset 136, which maybe configured to provide location information (e.g., longitude andlatitude) regarding the current location of the WTRU 102. In additionto, or in lieu of, the information from the GPS chipset 136, the WTRU102 may receive location information over the air interface 115/116/117from a base station (e.g., base stations 114 a, 114 b) or determine itslocation based on the timing of the signals being received from two ormore nearby base stations. It will be appreciated that the WTRU 102 mayacquire location information by way of any suitablelocation-determination method.

The processor 118 may further be coupled to other peripherals 138, whichmay include one or more software or hardware modules that provideadditional features, functionality, or wired or wireless connectivity.For example, the peripherals 138 may include various sensors such as anaccelerometer, biometrics (e.g., finger print) sensors, an e-compass, asatellite transceiver, a digital camera (for photographs or video), auniversal serial bus (USB) port or other interconnect interfaces, avibration device, a television transceiver, a hands free headset, aBluetooth® module, a frequency modulated (FM) radio unit, a digitalmusic player, a media player, a video game player module, an Internetbrowser, and the like.

The WTRU 102 may be included in other apparatuses or devices, such as asensor, consumer electronics, a wearable device such as a smart watch orsmart clothing, a medical or eHealth device, a robot, industrialequipment, a drone, a vehicle such as a car, truck, train, or anairplane. The WTRU 102 may connect to other components, modules, orsystems of such apparatuses or devices via one or more interconnectinterfaces, such as an interconnect interface that may comprise one ofthe peripherals 138.

FIG. 32G is a block diagram of an exemplary computing system 90 in whichone or more apparatuses of the communications networks illustrated inFIG. 32A, FIG. 32C, FIG. 32D and FIG. 32E as well as power saving in NR,such as the systems and methods illustrated in FIG. 21 or FIG. 28 andothers described and claimed herein, such as certain nodes or functionalentities in the RAN 103/104/105, Core Network 106/107/109, PSTN 108,Internet 110, Other Networks 112, or Network Services 113. Computingsystem 90 may comprise a computer or server and may be controlledprimarily by computer readable instructions, which may be in the form ofsoftware, wherever, or by whatever means such software is stored oraccessed. Such computer readable instructions may be executed within aprocessor 91, to cause computing system 90 to do work. The processor 91may be a general purpose processor, a special purpose processor, aconventional processor, a digital signal processor (DSP), a plurality ofmicroprocessors, one or more microprocessors in association with a DSPcore, a controller, a microcontroller, Application Specific IntegratedCircuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, anyother type of integrated circuit (IC), a state machine, and the like.The processor 91 may perform signal coding, data processing, powercontrol, input/output processing, or any other functionality thatenables the computing system 90 to operate in a communications network.Coprocessor 81 is an optional processor, distinct from main processor91, that may perform additional functions or assist processor 91.Processor 91 or coprocessor 81 may receive, generate, and process datarelated to the methods and apparatuses disclosed herein for power savingin NR.

In operation, processor 91 fetches, decodes, and executes instructions,and transfers information to and from other resources via the computingsystem's main data-transfer path, system bus 80. Such a system busconnects the components in computing system 90 and defines the mediumfor data exchange. System bus 80 typically includes data lines forsending data, address lines for sending addresses, and control lines forsending interrupts and for operating the system bus. An example of sucha system bus 80 is the PCI (Peripheral Component Interconnect) bus.

Memories coupled to system bus 80 include random access memory (RAM) 82and read only memory (ROM) 93. Such memories include circuitry thatallows information to be stored and retrieved. ROMs 93 generally includestored data that cannot easily be modified. Data stored in RAM 82 may beread or changed by processor 91 or other hardware devices. Access to RAM82 or ROM 93 may be controlled by memory controller 92. Memorycontroller 92 may provide an address translation function thattranslates virtual addresses into physical addresses as instructions areexecuted. Memory controller 92 may also provide a memory protectionfunction that isolates processes within the system and isolates systemprocesses from user processes. Thus, a program running in a first modemay access only memory mapped by its own process virtual address space;it cannot access memory within another process's virtual address spaceunless memory sharing between the processes has been set up.

In addition, computing system 90 may include peripherals controller 83responsible for communicating instructions from processor 91 toperipherals, such as printer 94, keyboard 84, mouse 95, and disk drive85.

Display 86, which is controlled by display controller 96, is used todisplay visual output generated by computing system 90. Such visualoutput may include text, graphics, animated graphics, and video. Thevisual output may be provided in the form of a graphical user interface(GUI). Display 86 may be implemented with a CRT-based video display, anLCD-based flat-panel display, gas plasma-based flat-panel display, or atouch-panel. Display controller 96 includes electronic componentsrequired to generate a video signal that is sent to display 86.

Further, computing system 90 may include communication circuitry, suchas for example a wireless or wired network adapter 97, that may be usedto connect computing system 90 to an external communications network ordevices, such as the RAN 103/104/105, Core Network 106/107/109, PSTN108, Internet 110, WTRUs 102, or Other Networks 112 of FIG. 32A, FIG.32B, FIG. 32C, FIG. 32D, or FIG. 32E, to enable the computing system 90to communicate with other nodes or functional entities of thosenetworks. The communication circuitry, alone or in combination with theprocessor 91, may be used to perform the transmitting and receivingsteps of certain apparatuses, nodes, or functional entities describedherein.

It is understood that any or all of the apparatuses, systems, methodsand processes described herein may be embodied in the form of computerexecutable instructions (e.g., program code) stored on acomputer-readable storage medium which instructions, when executed by aprocessor, such as processors 118 or 91, cause the processor to performor implement the systems, methods and processes described herein.Specifically, any of the steps, operations, or functions describedherein may be implemented in the form of such computer executableinstructions, executing on the processor of an apparatus or computingsystem configured for wireless or wired network communications. Computerreadable storage media includes volatile and nonvolatile, removable andnon-removable media implemented in any non-transitory (e.g., tangible orphysical) method or technology for storage of information, but suchcomputer readable storage media do not include signals. Computerreadable storage media include, but are not limited to, RAM, ROM,EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD) or other optical disk storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other tangible or physical medium which may be used to store thedesired information and which may be accessed by a computing system.

In describing preferred methods, systems, or apparatuses of the subjectmatter of the present disclosure—power saving in NR—as illustrated inthe Figures, specific terminology is employed for the sake of clarity.The claimed subject matter, however, is not intended to be limited tothe specific terminology so selected, and it is to be understood thateach specific element includes all technical equivalents that operate ina similar manner to accomplish a similar purpose.

The various techniques described herein may be implemented in connectionwith hardware, firmware, software or, where appropriate, combinationsthereof. Such hardware, firmware, and software may reside in apparatuseslocated at various nodes of a communication network. The apparatuses mayoperate singly or in combination with each other to effectuate themethods described herein. As used herein, the terms “apparatus,”“network apparatus,” “node,” “device,” “network node,” or the like maybe used interchangeably. In addition, the use of the word “or” isgenerally used inclusively unless otherwise provided herein.

This written description uses examples to disclose the invention,including the best mode, and also to enable any person skilled in theart to practice the invention, including making and using any devices orsystems and performing any incorporated methods. The patentable scope ofthe invention is defined by the claims, and may include other examplesthat occur to those skilled in the art (e.g., skipping steps, combiningsteps, or adding steps between exemplary methods disclosed herein). Suchother examples are intended to be within the scope of the claims if theyhave structural elements that do not differ from the literal language ofthe claims, or if they include equivalent structural elements withinsubstantial differences from the literal languages of the claims.

In the discussions herein, the signal used to send the UE to micro-sleepmay be referred to as a go-to-sleep (GTS) signal. The signal used towake-up a UE that is in sleep mode may be referred to as a wake-upsignal. The wake-up and GTS signals are referred to a power savingssignal in the remainder of the discussions. Although specific examplesmay apply to the wake-up signal or GTS, the solutions applicable to onesignal may also apply to the other signal.

Methods, systems, apparatuses (e.g., user equipment), or computerreadable storage mediums, among other things, as described herein mayprovide for means for power saving mechanisms in new radio. A method,system, computer readable storage medium, or apparatus has means forperiodically monitoring PDCCH for the wake-up trigger providing anaperiodic TRS; and when the UE receives the wake-up trigger, switchingback to BWP_(W), and using the aperiodic TRS to fine tune its timing andfrequency. A method, system, computer readable storage medium, orapparatus has means for waking up when an OnDuraction occurs for theuser equipment; during the OnDuration, monitoring PDCCH for the wake-uptrigger on the first monitoring occasion; and when the UE receives thewake-up trigger of a PDCCH on the first monitoring occasion, waking up;or else sleeping and not monitoring other occasions in the OnDuration. Amethod, system, computer readable storage medium, or apparatus has meansfor obtaining a message for multiple power savings configurations (PSCs)for the user equipment; and activating one of the PSCs based on atraffic condition or an application. A method, system, computer readablestorage medium, or apparatus has means for operating in a dormant statewhen the user equipment is in an RRC-Connected mode; and based on beingin the dormant state performing one or more of the following: 1)reporting measurements or tracking through the PCell or PSCell; or 2)monitoring for activation which is indicated on the PCell or PSCellthrough higher layer signaling or through L1 signaling and restrictingthe number of blind decodes. A method, system, computer readable storagemedium, or apparatus has means for bundling SCells supplement the PCellor PSCell. A method, system, computer readable storage medium, orapparatus has means for when sending an SR that is on a PCell or SCell,activating a bundle that was in a dormant state. A method, system,computer readable storage medium, or apparatus has means for receiving apower saving signal through a DL control information in its DRX activetime indicating it to sleep; and UE sleeps on receiving it. A method,system, computer readable storage medium, or apparatus based onreceiving a power saving signal with a command to sleep in the activeduration of the DRX, on detecting the power savings signal, goes tosleep until the next monitoring occasion of the power savings signal. Asignal (e.g., control signal) may be an UL or DL grant. The field ofcontrol signal in indicating the BWP for the grant may be reused toindicate the power saving state. All combinations in this paragraph andthe following paragraph (including the removal or addition of steps) arecontemplated in a manner that is consistent with the other portions ofthe detailed description.

Methods, systems, apparatuses (e.g., user equipment), or computerreadable storage mediums, among other things, as described herein mayprovide for means for power saving mechanisms in new radio. A method,system, computer readable storage medium, or apparatus has means forwaking up prior to the apparatus (e.g., UE) OnDuration to monitor apower savings signal in a monitoring occasion which may be configuredthrough RRC signaling; based on detecting the power savings signal,determining if it must monitor the subsequent OnDuration (e.g., thefollowing onDuration, which may be the immediate OnDuration followingthe monitoring occasion); if the power savings signal indicates it towake-up, the apparatus may monitor the subsequent OnDuration; and if thepower savings signal indicates the apparatus to go to sleep, theapparatus may not monitor the subsequent OnDuration and the UE may sleepuntil the next monitoring period for the power savings signal. Since themonitoring occasion for power savings signal occurs prior to onDuration,the following OnDuration may refer to the onDuration coming after(usually immediately after) the monitoring occasion for power savingssignal. The power savings signal may be indicated through the DL controlsignal. The DL control signal may be configured in a UE-specific manneror in a in a multi-cast manner that may be received by multiple UEs(e.g., group common PDCCH). UE-specific manner may be considered as aUE-specific identifier may be used for the control signal. So only a UEthat has that identifier may decode it. With regard to multi-castmanner, multiple UEs be configured with the same identifier, so when acontrol signal with that identifier is signaled, they can decode it. Ifthe apparatus does not detect the power savings signal in the monitoringoccasion, it may wake up to monitor the next OnDuration. If theapparatus does not detect the power savings signal in the monitoringoccasion, it may go to sleep and may not monitor the next OnDuration.The apparatus may monitor the power savings signal in first BWP andswitch to second BWP to monitor the OnDuration. The first BWP and secondBWP may be different. The DL control signal may be identified through anidentifier MS-RNTI that is configured to the UE through RRC. The powersavings signal may be monitored on resources exclusively allocated forthe power savings signal. If the UE fails to detect a power savingssignal, it wakes up to monitor the OnDuration (as if it detected thepower savings signal). A method, system, computer readable storagemedium, or apparatus has means for waking up to monitor a power savingssignal (which may be in a radio resource control-configured monitoringoccasion or the like) prior to an OnDuration of a discontinuousreception cycle on Celli (e.g., a first cell); based on the powersavings signal, determining whether to monitor a subsequent OnDuration;and determining, based on a command received on Celli, a behavior toactivate, deactivate, wake-up, or sleep on other cells monitored by theapparatus. A method may monitor an indication to sleep in the activetime of the discontinuous reception cycle (that may be during whengrants are received); and based on receiving the indication to sleep inthe active time which may be of the discontinuous reception cycle,switch to a lower power state of operation until the next monitoringoccasion of the power savings signal. Active time may be considered theOnDuration or period when the drxInactivityTimer is running. Active timemay denote OnDuration+drxInactivitytimer. All combinations in thisparagraph and the previous paragraphs (including the removal or additionof steps) are contemplated.

1. An apparatus that performs wireless communication, the apparatuscomprising: a processor; and a memory coupled with the processor, thememory comprising executable instructions stored thereon that whenexecuted by the processor cause the processor to effectuate operationscomprising: waking up to monitor a power savings signal in a monitoringoccasion prior to an OnDuration of a discontinuous reception cycle on afirst cell; detecting the power savings signal in the monitoringoccasion; based on the power savings signal, determining whether tomonitor a subsequent OnDuration, wherein the determining comprises: whenthe power savings signal comprises an indication to wake-up, monitoringthe subsequent OnDuration on the first cell, when the power savingssignal comprises an indication to sleep, not monitoring the subsequentOnDuration on the first cell; and determining, based on a commandreceived on the first cell, a behavior to activate, deactivate, wake-up,or sleep on a second cell monitored by the apparatus.
 2. The apparatusof claim 1, the operations further comprising when the power savingssignal comprises an indication to sleep, sleeping until a nextmonitoring period for the power savings signal.
 3. The apparatus ofclaim 1, the operations further comprising: monitoring the power savingssignal in a first bandwidth part; and switching to a second bandwidthpart to monitor the OnDuration.
 4. The apparatus of claim 1, wherein thepower savings signal is indicated through a downlink control signal. 5.The apparatus of claim 1, wherein the power savings signal is indicatedthrough a downlink control signal, wherein the downlink control signalis configured in an apparatus-specific manner, wherein the apparatus isa user equipment.
 6. The apparatus of claim 1, wherein the power savingssignal is indicated through a downlink control signal, wherein thedownlink control signal is configured in a multi-cast manner, receivedby multiple UEs.
 7. The apparatus of claim 1, wherein the power savingssignal is indicated through a downlink control signal, wherein thedownlink control signal is identified through an identifier ofmicrosleep-radio network temporary identification that is configured tothe apparatus through the radio resource control signaling.
 8. Theapparatus of claim 4, wherein the power savings signal is monitored onresources exclusively allocated through radio resource control signalingfor the power savings signal.
 9. The apparatus of claim 1, theoperations further comprising when the apparatus fails to detect a powersaving signal, waking up to monitor the subsequent OnDuration.
 10. Theapparatus of claim 1, the operations further comprising: furthermonitoring an indication to sleep in the active time of thediscontinuous reception cycle during which grants may be received; andbased receiving the indication to sleep in the active time of thediscontinuous reception cycle, switching to a lower power state ofoperation until the next monitoring occasion of the power savingssignal.
 11. A method for wireless communication, the method comprising:waking up, by an apparatus, to monitor a power savings signal in a radioresource control-configured monitoring occasion prior to an OnDurationof a discontinuous reception cycle on a first cell; detecting the powersavings signal in the monitoring occasion; based on the power savingssignal, determining whether to monitor a subsequent OnDuration, whereinthe determining comprises: when the power savings signal comprises anindication to wake-up, monitoring the subsequent OnDuration on the firstcell, when the power savings signal comprises an indication to sleep,not monitoring the subsequent OnDuration on the first cell; anddetermining, based on a command received on the first cell, a behaviorto activate, deactivate, wake-up, or sleep on a second cell monitored bythe apparatus.
 12. The method of claim 11, further comprising when thepower savings signal comprises an indication to sleep, sleeping until anext monitoring period for the power savings signal.
 13. The method ofclaim 11, further comprising: monitoring the power savings signal in afirst bandwidth part; and switching to a second bandwidth part tomonitor the OnDuration.
 14. The method of claim 11, wherein the powersavings signal is indicated through a downlink control signal.
 15. Themethod of claim 11, wherein the power savings signal is indicatedthrough a downlink control signal, wherein the downlink control signalis configured in an apparatus-specific manner, wherein the apparatus isa user equipment.
 16. The method of claim 11, wherein the power savingssignal is indicated through a downlink control signal, wherein thedownlink control signal is configured in a multi-cast manner, receivedby multiple UEs.
 17. The method of claim 11, wherein the power savingssignal is indicated through a downlink control signal, wherein thedownlink control signal is identified through an identifier ofmicrosleep-radio network temporary identification that is configured tothe apparatus through the radio resource control signaling.
 18. Themethod of claim 14, wherein the power savings signal is monitored onresources exclusively allocated for the power savings signal.
 19. Themethod of claim 11, further comprising when the apparatus fails todetect a power saving signal, waking up to monitor the subsequentOnDuration.
 20. A computer-readable storage medium storing computerexecutable instructions that when executed by a computing device causesaid computing device to effectuate operations comprising: waking up tomonitor a power savings signal in a radio resource control-configuredmonitoring occasion prior to an OnDuration of a discontinuous receptioncycle on a first cell; detecting the power savings signal in themonitoring occasion; based on the power savings signal, determiningwhether to monitor a subsequent OnDuration, wherein the determiningcomprises: when the power savings signal comprises an indication towake-up, monitoring the subsequent OnDuration on the first cell, whenthe power savings signal comprises an indication to sleep, notmonitoring the subsequent OnDuration on the first cell; and determining,based on a command received on the first cell, a behavior to activate,deactivate, wake-up, or sleep on a second cell.